I have multiple teams working on the same project with a single backlog. Can I generate individual team reports (sprint burndown, story cycle time etc) as well as a whole project report for cumulative flow covering all teams?
Is this configuration (single JIRA project, multiple team boards) the best way to set this up or should I use multiple JIRA projects (one per team) and then create a rolled up cumulative flow via some other mechanism?
Advice gratefully received; thanks
It is totally up to you to create multiple projects or same project. One thing to consider here is that there is no cumulative rolled up burn down charts out of the box. You can have one board for multiple projects by creating a filter for them. In any case the burndown charts you will get will be for a specific sprint.
If the teams are doing similar work contributing towards a single big project, then in that case probably you will be better with one project and multiple boards under it.
Thanks Ravi, very helpful.
If we set it up then as one project with multiple boards sounds best. We can define which stories are worked on by which team with the Team field. Presumably then the same filter which creates the individual team boards can be used to see the reports by team (for Sprint Burndown); and the whole project with no filters could be used to see a Cumulative Flow report across the entire project (ie all teams)? Make sense?
Steve - would be good to know how this went -
I'm also trying to work out the best configuration.
We have multiple projects and multiple teams. Some projects are worked on by multiple teams, and some teams work on multiple projects.
We also want to track BAU workload, which some teams also have -
Considering setting up one "project" for each team where they can manage all tasks. then setting filters for boards that track projects.
Any thoughts or advice welcome.
After much discussion... we went with a single project, multiple scrums; backlog split by 'Responsible Team' and much use of components.
This worked well for us within the concept of the one big project but now we have delivered that we've learned and developed our thinking further, including need to incorporate the operational BAU workload across the whole IT function. Which has led us now to somewhere slightly different but which also supports the project delivery piece.
So we now have Jira Projects by Product (eg we have a CRM Product/Project and a Reporting Product/Project). All work that touches that product, regardless of source, goes into the Jira backlog for that Product and is worked on when it is prioritised. It forces a lot more discussion between Project Managers and Product Owners and much more holistic working across teams. Still early days and many teething issues which we've overcome but I genuinely believe this is the best model for any organisation wanting to move to Agile delivery models, including within the BAU/Operations space. Still got some ITIL folk to win over :-).
Steve - thanks.
We're going to try one 'JIRA project' per team allowing each team to set their 'components' and team managers to set workflows. We'll use boards to represent our 'projects' which cross cut the teams.
Based on what I know, this makes sense, but please shout if you see any pitfalls in this plan.
- good luck with those ITIL folk.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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