Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

One Product Backlog with multiple SCRUM teams

Does anyone have a suggestion for managing the following:

One product backlog

2 Boards - each for one SCRUM team

How can I have sprints running for each board pulling the items from one central backlog?

Thank you for your assistance!

1 answer

Hi Landi,
it was mentioned in multiple topics - like https://community.atlassian.com/t5/Jira-Software-questions/One-project-multiple-backlog-multiple-sprints/qaq-p/806493

Quick answer.
Set up a separate scrum board for each team.
Have a filter for each board that filters out issues based on some differentiator:
* e.g. 1 component="Team-X"  / "Team-Y" etc.

* e.g.2 label = "Team-X"  / "Team-Y" etc.

You can have many components per issue, so you can still use components like they should be used :) 
People say that benefit of components over labels here is that sub-tasks created under a story with a component assigned should get the component automatically (so it will stay with the board and its filter)

I've set it up - tried both with teams in labels and teams in components; it works but subtasks inherit neither labels nor components -> from a quick search it seems like you'd need a plugin for that

I've tried to set this up, but from Board-X I can still see the sprint created on Board-Y.
Any thoughts?

Hi Luis,

check if your task have both components.

If a task has both, then it is picked up by both filters (each board); if it is in a specific sprint, then it will show with that sprint as well; 

so the way to do this is to have only one component per task, or share sprints among teams (though you'd have to start and close them together then);

there might be also some other edge cases - but I don't have enough info to support; the one I described is a typical mistake I've noticed;

 

BTW - I've been working with this setup for 6+ months and it works very well; I actually prefer it to the "separate teams = separate projects" approach

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

750 views 12 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you