Your SlideShare is downloading. ×
Qcon multi team sprint planning
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Qcon multi team sprint planning

772
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
772
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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. Scrum topology PO Product 1 1-* Product 1 1-* Team Owner BacklogHenrik Kniberg 2
  • 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 POHenrik Kniberg
  • 4. How to form teams?Henrik Kniberg 4
  • 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. Self-organizing to form new teamsConstraints:• 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. Product backlog – 1 or many?PO PO Henrik Kniberg 7
  • 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 POHenrik Kniberg
  • 9. Just before the meeting startsHenrik Kniberg 9
  • 10. Sprint demoHenrik Kniberg 10
  • 11. Introduction & backlog summaryHenrik Kniberg 11
  • 12. Preliminary backlog allocationHenrik Kniberg 12
  • 13. Scrum of scrums discussing the big pictureHenrik Kniberg 13
  • 14. Preliminary backlog allocationHenrik Kniberg 14
  • 15. Negotiating about backlog allocationHenrik Kniberg 15
  • 16. Product owners resolving priority problem Henrik Kniberg 16
  • 17. Task breakdown per teamHenrik Kniberg 17
  • 18. WrapupHenrik Kniberg 18
  • 19. Meeting retrospectiveHenrik Kniberg 19
  • 20. Typical challenges People getting bored or feeling inefficient Priority & dependency problems discovered Fatigue ”Shared resources” & specialists Running out of timeHenrik Kniberg 20
  • 21. RecommendationsMake sure product backlog is ready before the meeting Priorities must be clear Have a preplanning meeting with POs if necessaryGo to separate location with nice, social atmosphereReserve 4- 8 hours (depending on number of teams)Start with wrapup of previous sprint... then do high-level sprint goal at beginning of meetingAnalog tools (index cards, post-its, flipcharts) rather than computersProduct owners present (or nearby) all the timeEncourage standingMake sure each team has a definition of doneTemplates are useful for new teams1 hour timeboxes Clear goal (”definition of done”) for each timebox Scrum-of-scrums between each timeboxHandle dependency & priority problems immediately (”stop the line”)Many breaks, lots of fruitKeep all teams until the endEnd with wrapup & meeting retrospectiveHenrik Kniberg 21
  • 22. That’s it! Thanks?

×