Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to setup 2 sprint teams with a common backlog and Individual back log for the team

HI can someone share how to setup 

  • 2 sprint teams and separate board for each with their own backlog
  • A common backlog which both team can share ,for EG. The item in common backlog can be moved a teams Individual backlog


1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 09, 2019

Hi @Naveen Rameshkumar

We've managed for a few similar scenarios. One was issues sat on a product backlog until a team picked them up, moving to their sprint backlog (usually a few sprints from expected delivery). The other was pre-delivery the work was done via Kanban - moving to Scrum for delivery. 

This is how we handled each:

Product vs Sprint Backlog:

  • Created a Kanban Board for the Product Backlog. It had the initial pre-development statuses on the board in the Backlog Column, with a status that issues moved to to be classed as ready for delivery team involvement.
  • Issues sat in the Backlog until prioritised for a team's backlog - they then moved to that status and were assigned a Team (using another field - eg. Label).
  • Issues remained in the Backlog board if no Team was assigned - this showed that the data had not been correctly applied. If Team was applied, we filtered these out of the Backlog board.
  • Two separate sprint boards were then there for Teams to manage their own Backlogs / Delivery. These were based on applied Team and started in the assigned status.

Pre-Delivery vs Delivery:

  • We created a Kanban Board with a Backlog and pre-development statuses across the columns (eg. To Do, In Analysis, In Architecture)
  • The final status on this board was the status issues moved to when ready for delivery team involvement.
  • Like above, issues only disappeared if Team was applied - using filters on the Kanban board. If not, they remained on the Kanban Board to show they had no assigned team.

^ You can customise these approaches to your own needs, but this does allow you to have pre-delivery backlogs and a backlog per team.

A final option is to have just one Scrum Board and run parallel sprints - this means you would have one main Backlog but no separate backlogs for teams; upcoming work would be managed through the Active / Future Sprints created for each team.

Let me know if any of these are of interest, happy to provide more instructions on how to replicate them :)


Thanks I will Adopt the Final option , I believe that will work for Us


Thanks For your help

AUG Leaders

Atlassian Community Events