crisp multi team sprint planning
TRANSCRIPT
![Page 1: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/1.jpg)
Multi-team sprint planning
Henrik KnibergAgile & Lean coach at Crisp, Stockholmhttp://www.crisp.se/henrik.kniberg
Architect & developerMostly Java
ManagerCTO at three IT companies ≈40 developers
AuthorScrum and XP from the Trenches>100,000 readers, translated to 7 languages
Coach & teacherAgile & lean coachWork with Jeff Sutherland & Mary PoppendieckRegularly speak at international conferences
QCon Beijing2009-04-07
![Page 2: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/2.jpg)
Henrik Kniberg
Scrum topology
2
PO
ProductBacklog Team
ProductOwner
1-*11-*1
![Page 3: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/3.jpg)
Henrik Kniberg
Scrum topology
ProductBacklog Team
ProductOwner
1-*11-*1
1 1 1
1 1 2
1 2 1
1 2 2
2 1 1
2 1 2
2 2 1
2 2 2
PO
PO
PO
PO
PO
CPO
![Page 4: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/4.jpg)
Henrik Kniberg
How to form teams?
4
![Page 5: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/5.jpg)
Henrik Kniberg
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
5
Case 1: Bootstrapping agile teams
![Page 6: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/6.jpg)
Henrik Kniberg
Constraints:• 3-8 people per team• Team has PO• Focused & dedicated to shared goal• Independent (can deliver whole story)
Self-organizing to form new teams
CombinedCombined
New
Preliminary team allocation After a week in the kitchen
![Page 7: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/7.jpg)
Henrik Kniberg
Product backlog – 1 or many?
7
PO PO
![Page 8: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/8.jpg)
Henrik Kniberg
Multi-team sprint planningSample agenda
9:00 Welcome. Sprint review & retrospective.10:00 Goals & priorities for next sprint11:00 Preliminary backlog allocation12:00 Lunch 13:00 Preliminary commitment per team14:00 Task breakdown & final commitment per team16:00 Wrapup
PO
![Page 9: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/9.jpg)
Henrik Kniberg
Just before the meeting starts
9
![Page 10: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/10.jpg)
Henrik Kniberg
Sprint demo
10
![Page 11: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/11.jpg)
Henrik Kniberg
Introduction & backlog summary
11
![Page 12: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/12.jpg)
Henrik Kniberg
Preliminary backlog allocation
12
![Page 13: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/13.jpg)
Henrik Kniberg
Scrum of scrums discussing the big picture
13
![Page 14: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/14.jpg)
Henrik Kniberg
Preliminary backlog allocation
14
![Page 15: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/15.jpg)
Henrik Kniberg
Negotiating about backlog allocation
15
![Page 16: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/16.jpg)
Henrik Kniberg
Product owners resolving priority problem
16
![Page 17: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/17.jpg)
Henrik Kniberg
Task breakdown per team
17
![Page 18: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/18.jpg)
Henrik Kniberg
Wrapup
18
![Page 19: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/19.jpg)
Henrik Kniberg
Meeting retrospective
19
![Page 20: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/20.jpg)
Henrik Kniberg
Typical challenges
People getting bored or feeling inefficientPriority & dependency problems discoveredFatigue”Shared resources” & specialistsRunning out of time
20
![Page 21: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/21.jpg)
Henrik Kniberg
RecommendationsMake sure product backlog is ready before the meeting
Priorities must be clearHave a preplanning meeting with POs if necessary
Go 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 standing Make sure each team has a definition of doneTemplates are useful for new teams1 hour timeboxes
Clear goal (”definition of done”) for each timeboxScrum-of-scrums between each timebox
Handle dependency & priority problems immediately (”stop the line”)Many breaks, lots of fruitKeep all teams until the endEnd with wrapup & meeting retrospective
21
![Page 22: Crisp Multi Team Sprint Planning](https://reader033.vdocuments.us/reader033/viewer/2022052603/55d4d702bb61ebeb488b46b2/html5/thumbnails/22.jpg)
That’s it! Thanks?