TWELVE Agile AdoptionFailure Modesnyspin.org/Barry Mullan - 12 Agile Adoption Failure Modes.pdf12...
Transcript of TWELVE Agile AdoptionFailure Modesnyspin.org/Barry Mullan - 12 Agile Adoption Failure Modes.pdf12...
12 Agile Adoption Failure Modes
1
TWELVE Agile Adoption Failure Modes
Barry Mullan, Rally Software
About Me
http://bit.ly/12-failure-modes
A Better Approach
WAY
12 Agile Adoption Failure Modes
2
WASTEREDUCE
ELIMINATE
PRODUCTIONAlways, 7%
Often, 13%
Sometimes,
16%
Rarely
Used, 19%
Never
Used, 45%
UNECESSARY
Standish Group Study, reported by CEO Jim Johnson, XP2002
64% of Product
Features Never or
Rarely Used
WAITING
PROCESSING STEP
FOR THE
NEXT
ATTACK
POOR
QUALITY
12 Agile Adoption Failure Modes
3
AVOIDCONTEXT
SWITCHING
ERADICATEPROJECT
RISKS
DELIVER
HIGHEST VALUE FIRST
RELEASEEARLY AND OFTEN
12 Agile Adoption Failure Modes
4
MEASUREOUTCOMESNOT OUTPUTS
FASTFAIL
Failure Mode
#1
12 Agile Adoption Failure Modes
5
checkbookcommitments
unengaged
JUST DO IT!
immediateRESULTS
Organizational
Change
12 Agile Adoption Failure Modes
6
samemetrics
Failure Mode
#2
Culture that doesn’tSupport CHANGE
FOLLOWthe PLAN
12 Agile Adoption Failure Modes
7
ENFORCEDStandard of Work
Governance = Conformance
Standard of Work is static
Cross-organizational uniform
Detailed documentation
PMO as enforcers
Failure Mode
#3
RetrospectivesIneffective use of
12 Agile Adoption Failure Modes
8
Retrospectiveswhat we mean by
NONE
Ignored
There is
absolutely
nothing
wrong!
NOAction
12 Agile Adoption Failure Modes
9
Failure Mode
#4
ignore needed
INFRASTRUCTURE
StableEnvironment?
TANSTAAFL
12 Agile Adoption Failure Modes
10
Failure Mode
#5
lack of fullplanning participation
why?
12 Agile Adoption Failure Modes
11
who can commit?
waiting for decisions =
WASTE
conversation
more INSIGHTS
12 Agile Adoption Failure Modes
12
commitment
Failure Mode
#6
unavailableproduct owner
too manyproduct owners
12 Agile Adoption Failure Modes
13
AGILE asksA LOT of
Product Owners
communicatingtoo busy for all the
AGREEMENT
on Priorities
commitment
with team
12 Agile Adoption Failure Modes
14
Failure Mode
#7
bad scrum masters
COMMANDCONTROL
an
d
low moraleLower IQs
an
d
12 Agile Adoption Failure Modes
15
serve andfacilitate
removeimpediments
Cleanmesses
up
Failure Mode
#8
12 Agile Adoption Failure Modes
16
not having anonsite evangelist
whocares?
wholistens?
remoteroadkill?
12 Agile Adoption Failure Modes
17
advise, motivate protect and serve
Failure Mode
#9
team lackingauthority
red tapedecisions
12 Agile Adoption Failure Modes
18
No forming, storming, norming,
performing
empowered teamsamplify learning
inspect and adapt
deliver
high performing
12 Agile Adoption Failure Modes
19
Failure Mode
#10
not pulledtesting
FORWARD
pushdeliver
to
pileddebt
up
12 Agile Adoption Failure Modes
20
pileddebt
up
STOPtheLINE
Failure Mode
#11
traditionalperformanceappraisals
12 Agile Adoption Failure Modes
21
manager’s yearlyevaluation
individualheroicsrewarded
frequent teamevaluation
team contributionrewarded
12 Agile Adoption Failure Modes
22
Failure Mode
#12
REVERTINGto form
CHANGE is HARD
What now?
12 Agile Adoption Failure Modes
23
12 Adoption Failure Modes
• “Checkbook commitments” from executive management
• A culture that does not support learning
• Ineffective use of the retrospective
• Failure to pay attention to the infrastructure required
• Inability to get everyone in the planning meetings
• Unavailable product owner, or too many product owners who can’t agree
• Bad ScrumMasters
• Not having an onsite evangelist for remote locations
• Teams lacking authority and decision-making ability
• Not pulling Testing forward into Definition of “Done”
• Continuing to rely on a performance appraisal system
• Reverting to form, embracing the evil we know
CALLACTION
Think about the 12 Agile Adoption Failure Modes
What ONE failure mode are you PREPARED to ATTACK?
Create an ACTION PLAN
Hold a SELF-RETROSPECTIVE 30 days from now
Put the date in your Blackberry RIGHT NOW!
TO This Way
To
Agile
Success
12 Agile Adoption Failure Modes
24