Crisp Multi Team Sprint Planning

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

Scrum topology PO Product 1 1-* Product 1 1-* Team Owner Backlog Henrik Kniberg 2

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

How to form teams? Henrik Kniberg 4

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

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

Product backlog – 1 or many? PO PO Henrik Kniberg 7

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

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 ”Shared resources” & specialists Running out of time Henrik Kniberg 20

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

That’s it! Thanks?

Crisp Multi Team Sprint Planning

by George Ang on Sep 18, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Crisp Multi Team Sprint Planning — Presentation Transcript