Hi Community,
I have a team which has been working on development of Product A and have a Kanban board for tracking this. Now this same team is going to start work on Product B (in addition to Product A) and we as team are trying to figure out the best way to setup the stories for Product B.
Background: We would have only one standup in which we would be discussing about both Product A & Product B.
Some of the options that I can think of are:
1. Add the stories of Product B on the existing board with Labels as Identifiers. This may look easy to manage the stand up and avoid maintaining 2 boards.
2. Setup a new board for Product B: My only reservation is managing 2 boards for same team and going through both the boards during stand ups.
Looking for suggestions/ideas as to how others are managing such scenarios.
Hi @Ritu Sharma
You can use a single board for both products
If you are using one project you can keep using the same board filter, e.g.:
If using a separate project for each product you could use a filter like:
Either way you can also use Labels or Components to identify which work item relates to which Product and then use quick filters to only show one product at a time, e.g.:
or
Have a look here for a quick description of labels vs components: https://community.atlassian.com/forums/Jira-questions/Re-What-is-the-difference-between-labels-and-components/qaq-p/1122281/comment-id/604686#M604686
Hi Ritu - Welcome to the Atlassian Community!
Are the products using a single Jira project? Or are their two Jira projects?
Either way, I would create a board that shows all tickets from both products.
Is the Team exactly the same for both products? Or are there some different members for each product but the majority of the Team is the same?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.