Determine what is the correct approch in JIRA, and correct agile practice
1) 1 Jira project with several related teams, each team with their own sprints
Questions for this approach=>
Each team has its own Product Backlog or they have one in common
2) Simply to have 1 project per scrum team?
Thanks in advance,
From what you have presented here I would have a project per team - option 2. However, more data about your use case may change my mind. You may be able to accomplish w/ single project using Components for each team but project/team would provide greater flexibility.
I have seen in the industry both cases, approach 1), is very common, my concern with it, is that it manages 1 common Product Backlog which breaks ceremonies like PBL refinement (grooming),...Am I right,? it means, JIRA doesn't allow you to have several product backlogs (it does for sprints but no for product backlogs), which tells me that JIRA is 1 project 1 product backlog, correct?
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs