Multi-team sprint planning
         QCon Beijing
         2009-04-07

           Henrik Kniberg
           Agile & Lean co...
Scrum topology



                 PO



  Product 1           1-*   Product   1   1-*
                                   ...
Scrum topology                                PO



 Product 1 1-* Product 1   1-*
                                 Team
 ...
How to form teams?




Henrik Kniberg       4
Case 1: Bootstrapping agile teams


    Who defines the teams?
        Option 1: Teams defined centrally
            + Wor...
Self-organizing to form new teams
Constraints:
• 3-8 people per team
• Team has PO
• Focused & dedicated to shared goal
• ...
Product backlog – 1 or many?




PO                   PO




 Henrik Kniberg                 7
Multi-team sprint planning
   Sample agenda
      9:00       Welcome. Sprint review & retrospective.
      10:00      Goal...
Just before the meeting starts




Henrik Kniberg                   9
Sprint demo




Henrik Kniberg   10
Introduction & backlog summary




Henrik Kniberg                   11
Preliminary backlog allocation




Henrik Kniberg                   12
Scrum of scrums discussing the big picture




Henrik Kniberg                          13
Preliminary backlog allocation




Henrik Kniberg                   14
Negotiating about backlog allocation




Henrik Kniberg                         15
Product owners resolving priority problem




  Henrik Kniberg                            16
Task breakdown per team




Henrik Kniberg            17
Wrapup




Henrik Kniberg   18
Meeting retrospective




Henrik Kniberg          19
Typical challenges

   People getting bored or feeling inefficient
   Priority & dependency problems discovered
   Fatigue...
Recommendations
Make sure product backlog is ready before the meeting
      Priorities must be clear
      Have a preplann...
That’s it! Thanks?
Upcoming SlideShare
Loading in …5
×

Crisp Multi Team Sprint Planning

1,640 views

Published on

Published in: Technology, Sports
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,640
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
55
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Crisp Multi Team Sprint Planning

  1. 1. Multi-team sprint planning QCon Beijing 2009-04-07 Henrik Kniberg Agile & Lean coach at Crisp, Stockholm http://www.crisp.se/henrik.kniberg Architect & developer Mostly Java Manager CTO at three IT companies ≈40 developers Author Scrum and XP from the Trenches >100,000 readers, translated to 7 languages Coach & teacher Agile & lean coach Work with Jeff Sutherland & Mary Poppendieck Regularly speak at international conferences
  2. 2. Scrum topology PO Product 1 1-* Product 1 1-* Team Owner Backlog Henrik Kniberg 2
  3. 3. Scrum topology PO Product 1 1-* Product 1 1-* Team Owner Backlog PO 1 1 1 1 1 2 1 2 1 1 2 2 PO 2 1 1 2 1 2 2 2 1 PO 2 2 2 CPO PO Henrik Kniberg
  4. 4. How to form teams? Henrik Kniberg 4
  5. 5. Case 1: Bootstrapping agile teams Who defines the teams? Option 1: Teams defined centrally + Works + Fast - Lack of buy-in - Doesn’t harness collective knowledge Option 2: Teams form themselves from scratch + Harnesses collective knowledge + Buy-in - Slow - Might not work Option 3: Combination of 1 + 2. Preliminary teams defined centrally, teams then allowed to reform themselves + Works + Harnesses collective knowledge + Buy-in Henrik Kniberg 5
  6. 6. Self-organizing to form new teams Constraints: • 3-8 people per team • Team has PO • Focused & dedicated to shared goal • Independent (can deliver whole story) Combined Combined Preliminary team allocation After a week in the kitchen New Henrik Kniberg
  7. 7. Product backlog – 1 or many? PO PO Henrik Kniberg 7
  8. 8. Multi-team sprint planning Sample agenda 9:00 Welcome. Sprint review & retrospective. 10:00 Goals & priorities for next sprint 11:00 Preliminary backlog allocation 12:00 Lunch 13:00 Preliminary commitment per team 14:00 Task breakdown & final commitment per team 16:00 Wrapup PO Henrik Kniberg
  9. 9. Just before the meeting starts Henrik Kniberg 9
  10. 10. Sprint demo Henrik Kniberg 10
  11. 11. Introduction & backlog summary Henrik Kniberg 11
  12. 12. Preliminary backlog allocation Henrik Kniberg 12
  13. 13. Scrum of scrums discussing the big picture Henrik Kniberg 13
  14. 14. Preliminary backlog allocation Henrik Kniberg 14
  15. 15. Negotiating about backlog allocation Henrik Kniberg 15
  16. 16. Product owners resolving priority problem Henrik Kniberg 16
  17. 17. Task breakdown per team Henrik Kniberg 17
  18. 18. Wrapup Henrik Kniberg 18
  19. 19. Meeting retrospective Henrik Kniberg 19
  20. 20. Typical challenges People getting bored or feeling inefficient Priority & dependency problems discovered Fatigue ”Shared resources” & specialists Running out of time Henrik Kniberg 20
  21. 21. Recommendations Make sure product backlog is ready before the meeting Priorities must be clear Have a preplanning meeting with POs if necessary Go to separate location with nice, social atmosphere Reserve 4- 8 hours (depending on number of teams) Start with wrapup of previous sprint ... then do high-level sprint goal at beginning of meeting Analog tools (index cards, post-its, flipcharts) rather than computers Product owners present (or nearby) all the time Encourage standing Make sure each team has a definition of done Templates are useful for new teams 1 hour timeboxes Clear goal (”definition of done”) for each timebox Scrum-of-scrums between each timebox Handle dependency & priority problems immediately (”stop the line”) Many breaks, lots of fruit Keep all teams until the end End with wrapup & meeting retrospective Henrik Kniberg 21
  22. 22. That’s it! Thanks?

×