Hi, we have more (6) SCRUM teams, all of them work on same application (Old Spaghetti non-modular application) and so we have one product backlog for them. We start with 1 sprint for 1 team in JIRA Agile, so we always run 6 sprints in the same time. But then we can not constraint counts of issues in columns and calculation of velocity for each team is not very straightforward.
Is there any other way to solve our situation?
Thanks for all suggestions.
I would create 6 different agile boards (1 per team, since each team commits to their own sprint scope).
The data can be pulled from the same 'product' project: It's possible to define board data filter either on assignee (assignee in role / team members list + assignee is empty) or based on a specific field value (component, a custom-field (cfr. Christian), ... )
Also, I don't think you need to have 6 separate sprints as such.. at least not if all teams work on the same frequency (e.g. same sprint length, start & completion).
You can include common (sprint marker) issues on all boards & assigned to 1 specific sprint, in order to make the same Sprints appear on all boards / for all teams.
Note that such an approach does require that the sprint completion, planning & new sprint start are all happening in sync across teams.
Finally, since reports (velocity ) are based on agile board definition, the report data should be as expected.
Yes, it is possible to create sprints in each board separately. If you wish for each team to have their own sprint, that’s the way to go. You will also be able to see these sprints in the “main” board once any issue from the backlog was added into the sprint. These sprints will also appear in “main” board reporting.
I'm having a similar issue and want to confirm given the following scenario:
We have 1 jira project with two sprint boards (two scrum teams)
Can someone please confirm:
Each sprint board will show reporting (i.e. velocity, burndown) unique to each scrum team
The sprints will be the same across both scrum teams, so they will need to start and stop at the same time.
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