9 reasons why your Agile implementation might fail. A presentation inspired from Chris McGoff book, "Primes" - http://www.amazon.com/The-Primes-ebook/dp/B004HIM4UU/ Presented at OpenAgileRo 2011

1. Why an Agile
implementation might fail
few things that you should be aware when you decide to
implement Agile
a presentation facilitated by Radu Davidescu

2. Can Agile implementations fail?
Unless facilitated by Chuck Norris, YES, Agile implementations can
fail!

3. Agile implementations might
fail because …
! change <> transformation ! you are still attached and not
committed to a result
! transformation is perceived
differently by different team ! you pursue total consensus
members
! doing Agile <> being Agile
! formal leaders lose
consistency ! you try to implement Agile
! informal leaders are laggards ! implementations might fail

4. change <> transformation
Change Transformation
! change is creating a better ! transformation is creating
past in the future (like a new future
cheaper, faster, easier and
so on)
Change is not merely necessary to life — it is life. Alvin Toffler, in Future Shock‎ (1970), p. 304

5. Transformation is
perceived differently by
different team
members
• Idealists are analytical
• Sentimentalists are emotional
• Mercenaries are financialy
driven

6. Formal leaders lose
consistency
! in Agile adoption formal leaders switch from
“command and control” and hierarchy to collaboration
and flat hierarchy
! defining certain rules where “command and control”
and traditional hierarchy will still apply and
maintaining consistency is critical for a successful Agile
implementation

7. Informal leaders are
laggards
Laggards are the guardians of the “status quo”. When
the informal leaders of the group are laggards, Agile
adoption might be in great danger!

8. You are still attached and not
committed to a result
Attached Committed
! A strong bonding towards ! Being bound
or with. emotionally/intellectually
to a course of action or to
! A dependence, especially another person/other
a strong one. persons.
! The trait of sincerity and
focused purpose.
Wiktionary definitions

9. Recommended consensus
points:
You pursue ! The process was explicit,
total consensus rational and fair
Agile is about diversity, yet the ! I was treated well and my
trap of total consensus it’s there. inputs were heard
Everyone voice need to be heard.
! I can live with and I
Establish point of consensus.
commit to the outcomes

10. doing Agile <> being Agile
“You are now ScrumMasters! Prepare to be frustrated!”
Robin Dymond – my CST

11. You try to
! Your goal should feed
implement your motivation
Agile ! Agile is a methodology,
To make it work you need a some even consider it a
better, brighter purpose. It philosophy
should be clearly defined and
embraced by the team. ! Scrum is a process
Agile should be an agreed way of framework
reaching goals, not a goal!
! Backlog is a tool

12. Implementations
might fail
Sometimes, no matter how good you are,
how great circumstances look, how
positive conditions are, things might fail!

13. A final tip!
If you are going hire an Agile consultant that will present you only
success stories, think about it!
He might not be aware about the list discussed above.

14. I know you have questions,
so don’t be shy!
Thank you very much for your time!
Radu Davidescu
@rdavidescu / tsk.ro / rdavidescu@gmail.com