Suppose the following scenario:
1) Three multifunctionals teams
2) Single backlog for the three teams
What does Jira recommend, having either three boards or activating three Sprints at once?
Please, take into account metrics, for example burndown charts, cumulative flow, velocity, bugs, lead time, and so on
Hello @David Villacampa ,
This feels like a conflicting definition. Can you give more details?
Does a single backlog mean that every item in the backlog can go to someone in any of the teams? Or do teams work with specified subsets of the backlog?
You see, this is more of a process question than a Jira one. Whichever path you take, Jira probably can provide a way to manage it.
If any Backlog Item can go to any of the teams, then I would say you it sounds more like a single team (with subgroups) than 3 separate teams. In that case, 1 board, 1 sprint, and 1 burndown should be used.
Think of it this way, each sprint is a chunk of the backlog that you want to get done. The burndown chart shows the overall progress within that sprint so you can see how close you are to getting that chunk done. Based on my limited knowledge of your use case, a single board and single sprint would be my first choice.
Having said that, please also note that Jira Cloud has a feature flag somewhere in the admin pages that allows you to enable "Parallel Sprints". As the name suggests, this feature allows you to create and start multiple sprints in parallel based on the same backlog. According to your process specifics, this might also help.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events