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

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

0 votes
Answer accepted

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 :)

Ste

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

 

Thanks For your help

Suggest an answer

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

On-demand: Fireside chat with Atlassian on scaling agile organizations

Scaling an agile organization and setting it up for success over the long term is a hard thing to do. We hear a common set of questions from customers all the time, questions like: Can agile scal...

3,947 views 2 17
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