16.01.2015 Views

Adoption Failure Modes - AccuRev

Adoption Failure Modes - AccuRev

Adoption Failure Modes - AccuRev

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TWELVE Agile<br />

<strong>Adoption</strong> <strong>Failure</strong> <strong>Modes</strong><br />

Jean Tabaka, Rally Software


Stories


www.onedaywithoutshoes.com


your<br />

It’s about caring for<br />

WORLD


growth


good


change


weird


“<br />

MOST<br />

have what appear to be<br />

suicidal tendencies”<br />

Organizations


your group


your organization


your customers


<strong>Failure</strong> Mode<br />

#1


checkbook<br />

commitments


JUST DO IT!<br />

unengaged


immediate<br />

RESULTS


Organizational<br />

Change


same<br />

metrics


<strong>Failure</strong> Mode<br />

#2


Culture that doesn’t<br />

Support CHANGE


FOLLOW<br />

the PLAN


Standard of Work<br />

ENFORCED<br />

Governance = Conformance<br />

Standard of Work is static<br />

Cross-organizational uniform<br />

Detailed documentation<br />

PMO as enforcers


<strong>Failure</strong> Mode<br />

#3


Ineffective use of<br />

Retrospectives


what we mean by<br />

Retrospectives


NONE


Ignored<br />

There is<br />

absolutel<br />

y nothing<br />

wrong!


NO<br />

Action


<strong>Failure</strong> Mode<br />

#4


ignore needed<br />

INFRASTRUCTURE


Stable<br />

Environment


TANSTAAFL


<strong>Failure</strong> Mode<br />

#5


lack of full<br />

planning participation


why


who can commit


more INSIGHTS


waiting for decisions =<br />

WASTE


<strong>Failure</strong> Mode<br />

#6


unavailable<br />

product owner


too many<br />

product owners


AGILE asks<br />

A LOT of<br />

Product Owners


on<br />

AGREEMENT<br />

Priorities


with<br />

commitment<br />

team


<strong>Failure</strong> Mode<br />

#7


COMMAND<br />

CONTROL<br />

and


low morale<br />

Lower IQs<br />

and


serve and<br />

facilitate


emove<br />

impediments


Clean<br />

messes<br />

up


<strong>Failure</strong> Mode<br />

#8


not having an<br />

onsite evangelist


who<br />

listens


can’t reap<br />

the benefits


emote<br />

roadkill


<strong>Failure</strong> Mode<br />

#9


team lacking<br />

authority


ed tape<br />

decisions


No forming,<br />

performing<br />

storming, norming,


empowered teams<br />

amplify learning


high performing


<strong>Failure</strong> Mode<br />

#10


testing<br />

not pulled<br />

FORWARD


push<br />

deliver<br />

to


piled<br />

debt<br />

up


piled<br />

debt<br />

up


Stable<br />

Environment


<strong>Failure</strong> Mode<br />

#11


traditional<br />

performance<br />

appraisals


manager’s yearly<br />

evaluation


individual<br />

heroics<br />

rewarded


frequent team<br />

evaluation


team contribution<br />

rewarded


<strong>Failure</strong> Mode<br />

#12


REVERTING<br />

to form


CHANGE<br />

is HARD


What now


12 <strong>Adoption</strong> <strong>Failure</strong> <strong>Modes</strong><br />

• “Checkbook<br />

commitments” from<br />

executive management<br />

• A culture that does not<br />

support learning<br />

• Ineffective use of the<br />

retrospective<br />

• <strong>Failure</strong> to pay attention to<br />

the infrastructure required<br />

• Inability to get everyone in<br />

the planning meetings<br />

• Unavailable product<br />

owner, or too many<br />

product owners who can’t<br />

agree<br />

• Bad ScrumMasters<br />

• Not having an onsite<br />

evangelist for remote<br />

locations<br />

• Teams lacking authority<br />

and decision-making ability<br />

• Not pulling Testing forward<br />

into Definition of “Done”<br />

• Continuing to rely on a<br />

performance appraisal<br />

system<br />

• Reverting to form,<br />

embracing the evil we<br />

know


TO<br />

CALL<br />

ACTION<br />

This Way<br />

To<br />

Agile<br />

Success<br />

Think about the 12 Agile <strong>Adoption</strong><br />

<strong>Failure</strong> <strong>Modes</strong><br />

What ONE failure mode are you PREPARED to ATTACK<br />

Create an ACTION PLAN<br />

Hold a SELF-RETROSPECTIVE 30 days from now<br />

Put the date in your Blackberry RIGHT NOW!


your<br />

It’s about caring for<br />

WORLD


TWELVE Agile<br />

<strong>Adoption</strong> <strong>Failure</strong> <strong>Modes</strong><br />

Jean Tabaka, Rally Software

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!