Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Whats is the better approach working with several teams on a single backlog? (Boards or Sprints)

Suppose the following scenario:
1) Three multifunctionals teams
2) Single backlog for the three teams

What does Jira recommend, having either three boards or activating three Sprints at once?
Please, take into account metrics, for example burndown charts, cumulative flow, velocity, bugs, lead time, and so on



2 answers

1 accepted

1 vote
Answer accepted

Hello @David Villacampa ,

This feels like a conflicting definition. Can you give more details?

Does a single backlog mean that every item in the backlog can go to someone in any of the teams? Or do teams work with specified subsets of the backlog?


I mean each item in the backlog can go to any team. It will be decided either in the Sprint Planning Meeting or in the Refinement meeting (LeSS framework)

Thanks and regards,


You see, this is more of a process question than a Jira one. Whichever path you take, Jira probably can provide a way to manage it.

If any Backlog Item can go to any of the teams, then I would say you it sounds more like a single team (with subgroups) than 3 separate teams. In that case, 1 board, 1 sprint, and 1 burndown should be used.

Think of it this way, each sprint is a chunk of the backlog that you want to get done. The burndown chart shows the overall progress within that sprint so you can see how close you are to getting that chunk done. Based on my limited knowledge of your use case, a single board and single sprint would be my first choice.

Having said that, please also note that Jira Cloud has a feature flag somewhere in the admin pages that allows you to enable "Parallel Sprints". As the name suggests, this feature allows you to create and start multiple sprints in parallel based on the same backlog. According to your process specifics, this might also help.

Thanks for your answer, we are going to activate parallel sprints!



1 vote
Laura Holton Community Leader May 11, 2021

Hi @David Villacampa 👋

I feel if you are looking to work on one single backlog then working in Sprints over Boards would be more beneficial for all the metrics you mentioned.

All the best,


Suggest an answer

Log in or Sign up to answer

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