How to set up multiple Scrum teams working on same set of Master User Stories within a Project

ANIRBAN MUKHOPADHYAY

Hi,

We have to set up a Project in JIRA where we will have multiple tracks (SCRUM Teams) working on a single list of Master User Stories. Each Scrum team will have their own tech stories/tasks associated with Master User Stories and each team will have their own Sprints. There are some level of dependencies across Scrum teams and hence the sequencing of Sprints & User story selection within the Sprints need some level of cross team planning. 

Looking for advice/guidance on how should we set up this project in JIRA so that

1. Each Scrum team will have their own backlog, Sprint Board, Sprint Cycle - Multiple Scrum Board and multiple Sprint-1/2/3 etc.. for different Scrum teams within same Project

2. Link the Tech stories within each Scrum to the Master User Stories and get the point-in-time view of the Master User stories at Project level

3. Generate Reports/metrics (Velocity, Burn down Chart at Scrum team level as well as Project level

Thanks

Anirban

Bhushan Nagaraj_zb9hek

Hi Anirban,

From the description you have provided, it appears that what you refer to as "Master User Stories", should be an Epic.

Each Scrum team can create their stories within their boards, with the Epic Link field set to the Epic.

Some guidance for the scenario you have described.

Each Scrum team will have their own backlog, Sprint Board, Sprint Cycle - Multiple Scrum Board and multiple Sprint-1/2/3 etc.. for different Scrum teams within same Project

Create a separate Jira project to track Epics. If a higher level than Epic is required, create a new Issue Type called Initiative, and use Portfolio for Jira to vizualize Initiatives, Epics and the linked stories from multiple teams. Create a separate Jira project per Scrum team where they track associated Stories to the Epic using the Epic Link field. They can also create Bugs, Tasks and any other issue types relevant to their own teams.

2. Link the Tech stories within each Scrum to the Master User Stories and get the point-in-time view of the Master User stories at Project level

Portfolio for Jira addresses this use case. Take a look at the documentation at

https://confluence.atlassian.com/jiraportfolioserver/tracking-progress-and-status-814212695.html

https://confluence.atlassian.com/jiraportfolioserver/using-the-scope-view-802170536.html

3. Generate Reports/metrics (Velocity, Burn down Chart at Scrum team level as well as Project level

You can create a separate board that includes all the Epics and Stories to view Velocity and Burndown across multiple teams. Alternatively, EazyBI, Arsenale DataPlane, and other add-ons provide more reporting functionality. I have provided a couple of examples below.

https://docs.eazybi.com/display/EAZYBIJIRA/Sprint+burn-down+or+burn-up+chart

http://www.arsenalesystems.com/docs/display/dataplane/Rolling+Up+Epic+Time+Estimates

If you are looking for further guidance on best practices, I suggest working with our Solution Partner network. Let me know if you require more info on this.

Hope that helps.