Professional Documents
Culture Documents
10 Ways To Screw Up With Scrum and XP
10 Ways To Screw Up With Scrum and XP
10 Ways To Screw Up With Scrum and XP
Henrik Kniberg
1: ScrumMaster
isnt is tech guru is too busy to do SM stuff is line manager is not dedicated to team does not know Scrum does not have an impediment backlog
SM
Impediment backlog
No impediment backlog Slow workstations No test environment No contact with customer Crowded office
4
Henrik Kniberg
2: Definition of Done
dont have a default DoD dont obey it is outside of teams control
Henrik Kniberg
3: Velocity
isnt known isnt used 3 is misused 100 concurrent users 8 death marches team asked to promise dates including stories that arent Done Yo-yo velocity EXAMPLE
Today is Aug 6 Sprint length = 2 weeks Velocity = 30 - 40
!! "!!
PO
At least
At most
4: Retrospective
Were too busy, lets just start the next sprint instead
doesnt happen doesnt result in a list of improvements improvements arent executed improvements arent followed up unwanted people at the meeting everybody doesnt talk
Velocity
1
10
11
12
13
Sprint
Henrik Kniberg 7
Sprint retrospective
Part 1: What happened?
LAN shootout
Team flow!
Sprint demo
Week 1
Week 2
Week 3
2008-04-03
Henrik Kniberg 8
Sprint retrospective
Part 2: What do we do differently next sprint?
2008-04-03
Henrik Kniberg 9
5: Team commitment
Team is pressured Team doesnt track & learn Always undercommitting Always overcommitting Velocity = 0 Not allowing slack Estimated Actual
40 30 30 30
Estimated Actual
30 28 33 30 30 30 30
10
40 40 40
Henrik Kniberg
30 30 30
40 50 60
6: Technical debt
Letting it pile up Ignoring it
Vmax Vactual
velocity
Vmax Vactual
velocity
Sustainable pace!
time
time
Henrik Kniberg
11
Definition of Done
.... bla bla .... No increased technical debt
Sustainable pace
First step
Second step
Slow down even more Start repaying debt
(optional)
Henrik Kniberg
12
7: Teamwork
Fixed roles Personal backlogs Not helping each other Implementing all stories in parallell External management
Henrik Kniberg
13
PBL doesnt exist PO PBL not visible 3 Never-ending stories 100 concurrent Too big stories users 8 PO without power or domain knowledge <> 1 PO PBL not maintained by PO PO surprised at sprint demo PO not prioritizing PO being a bottleneck
Henrik Kniberg
8
5 5
3
5 5
8
5
3
14
V
Apr 2008 May 2008 June 2008
2009
2010
Q3 2008 Q4 2008
2011
2009
2012
Henrik Kniberg
15
9: Mergophobia
No Done branch No branch policies Not integrating daily Not taking responsibility Hiding behind branches
Sorry, but
http://www.infoq.com/articles/agile-version-control
Day 4 Day 5 Day 6 Release!
Trunk
m1
m2
Team A work
Policy: Unit tested
a1
a2
a3
a4
Team B work
Policy: Unit tested
b1
b2
b3
Timeline
Henrik Kniberg
17
Oh you mean that thing that the ScrumMaster fiddles with sometimes?
Henrik Kniberg
18
Warning signs
Burndown
Henrik Kniberg
19
We should stop this agile stuff, since were obviously doing it all wrong
Problems are normal Never stop looking for problems Dont panic, dont despair Visible problem = killable problem = opportunity for improvement! Prioritize and fix problems - one by one! Look back once in a while and pat yourselves on the back
Henrik Kniberg
20
Henrik Kniberg
21
Henrik Kniberg
22