My organization has 2 SCRUM teams working on a large portfolio of websites, and we are currently evaluating how to set up our JIRA environment. I have some questions about setting this up and hope someone from the community could provide me with some thoughts:
Thanks in advance!
There are a number of different options open to you in how to handle this scenario.
The simplest is to use quick filters to select the work allocated to each Scrum team and then you can share a common backlog, sprint cadence and reporting.
A more complex option is to use 2 Scrum boards pulling from the same set of projects but with different content in each sprint. This would allow each team to work with their own cadence. By careful construction of the filter for each Scrum board you can include a common backlog.
A further option is to use the parallel sprints option. Which is available from Atlassian Labs.
All of the above can easily cope with your requirement to include stories from different websites. I assume these are reported in different JIRA projects. If you are not using Epics within your Scrum methodology you could map the epics to the different websites for reporting purposes. Although this will not work if a story applies to more than one website.
Without more detail of what you are trying to achieve in terms of reporting I am unclear as well as to what value Portfolio would add.
Hope this helps
Thank you for your help! I was thinking about using Atlassian Labs' parallel sprints option, as this seems most easy to manage two sprints at the same time. I believe the quick filters option is too broad for our reporting means, as this would mean there is only 1 sprint running.
I will try to explain what I am hoping to achieve in terms of reporting:
Instead of having reports built on the back of a certain sprint, we want to be able to create reports for each website. So let's say we have website A, B and C. Scrum team 1 has a sprint backlog including a number of stories for website A and B, and Scrum team 2 has a sprint backlog including stories for website B and C. Instead of having a report of how Scrum team 1 performed overall, we want to be able to see the overall progress of website B. So instead of reporting on a sprint, we want to narrow the reporting down to a specific website.
I hope you understand what I mean
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
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