Configuration Advice - Multiple Sprint Teams and Projects

[Declan_curzon-hepworth]

Hi,

I am looking for some advice on how to configure Jira for our company needs.

We have 5 sprint teams that work on adding new features to our product with a common code base for all our customers. Our projects are split into multiple epics, and different sprint teams will work on different epics within a single project. Each sprint team has a backlog comprising stories from different epics.

How can I configure Jira to meet these needs - currently from my analysis it looks as though a project is designed to only ever be allocated to a single team, and there isn't a way to manage backlogs across projects for each team.

[Jack Brickey]

Hi @Declan_curzon-hepworth , Jira is quite effective at supporting multiple teams on a single code base. With that said it is difficult to say how best to configure for your needs with the info provided. You might wish to have a single project and use Components to define the different teams focus (e.g. UI, Platform, Backend, etc) and run parallel sprints with a single backlog. Or, you may wish to have different projects for each team with their own backlogs. Either way I would likely recommend using Company Managed Project(s) here.

[Declan_curzon-hepworth]

If using a single project, can you have multiple backlogs (one for each team), or only a single backlog?

If I go down the route of using multiple projects, wouldn't that essentially mean that a project was a team?

[Jack Brickey]

Single backlog per project. 

I wouldn't declare it as a project equals a team, but rather a team has its own project. I guess it comes down to what these individual teams focus is. For example, if one of the teams focuses on the UI than the project is associated with all things UI.

[Declan_curzon-hepworth]

Is there a concept in Jira of a team backlog, rather than a project backlog, that can consist of issues from projects, that can be prioritised?