Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
EVAN LEYBOURN
AUTOPSY OF A
FAILED AGILE
PROJECT
Evan Leybourn
Lean / Agile Business Leader and Author
Melbourne, Australia
@eleybourn
http://theagiledirector.com
Project 1: Business Intelligence
Primary Cause of Failure:
Customer Engagement
SYMPTOM #1:
POOR
ENGAGEMENT AND
COMMUNICATION
SYMPTOM #2:
NO TRUST
BETWEEN
BUSINESS &TEAM
SYMPTOM #3:
LACK OF SUBJECT
MATTER EXPERTS
POORLY MANAGED
EXPECTATIONS
SYMPTOM #4:
MISUNDERSTANDING
BUSINESS VALUE
SYMPTOM #5:
‘A manufacturer is not through
with his customer when a sale is
completed. He has then only
started with his customer.’
- ...
PREVENTION #1:
DO YOU HAVE THE
RIGHT PRODUCT
OWNER?
PREVENTION #2:
HAVE YOU TRAINED
THE CUSTOMER &
PRODUCT OWNER?
PREVENTION #3:
ARE THERE CLEAR
AND AGREED
EXPECTATIONS?
Project 2: Telecommunications
Primary Cause of Failure:
Poor Planning
SYMPTOM #6:
CONFLICT BETWEEN
CUSTOMER AND
STRATEGIC WORK
SYMPTOM #7:
POORLY DEFINED
PROJECT GOALS
POORLY DEFINED
SUCCESS CRITERIA
SYMPTOM #8:
‘It is always wise to look ahead,
but difficult to look further than you
can see.’
- Winston Churchill, ~1960
PREVENTION #4:
IS THE SYSTEM
FRAMEWORK
AVAILABLE?
PREVENTION #5:
ARE THE GOALS
AND END STATE
CLEARLY DEFINED?
PREVENTION #6:
HAVE YOU PLANNED
THE INITIAL
ITERATIONS?
Project 3: Government
Primary Cause of Failure:
The Team
SYMPTOM #9:
POOR AWARENESS
OF THE WHY’S
BEHIND AGILE
SYMPTOM #10:
CHRONICALLY
UNDERSTAFFED
SYMPTOM #11:
MISSING REQUIRED
SKILLS
COMPETING
PRIORITIES
SYMPTOM #12:
SYMPTOM #13:
LOW TEAM
MORALE, TRUST
OR RESPECT
SYMPTOM #14:
POOR SUPPORT
FROM EXTERNAL
TEAMS (e.g. DBA)
SYMPTOM #15:
NOT DELIVERING
VALUE IN EACH
ITERATION
‘Treat your men as you would your
own beloved sons. And they will
follow you into the deepest valley.’
- Sun Tzu, ~6th Cen...
PREVENTION #7:
ARE YOU
RECRUITING FOR
AN AGILE TEAM?
HAVE YOU
FOCUSED ON
DEVELOPING TEAM
CAPABILITY?
PREVENTION #8:
PREVENTION #9:
CAN YOU POSTPONE
STORIES NEEDING
MISSING SKILLS?
IS YOUR TEAM
TRAINED IN AGILE?
PREVENTION #10:
Project 4: Information Management
Primary Cause of Failure:
Infrastructure
UNDER-
DEVELOPED
ARCHITECTURE
SYMPTOM #16:
SYMPTOM #17:
MISSING SUPPORT
DOCUMENTATION
SYMPTOM #18:
UNSTABLE
UPSTREAM
SYSTEMS & DATA
SYMPTOM #19:
POOR TEST TOOLS
AND DATA
‘Beautiful objects are wrought by
study through effort, but ugly
things are reaped automatically
without toil.’
- Democrit...
HAVE YOU BUILT
THE BASELINE
INFRASTRUCTURE?
PREVENTION #11:
PREVENTION #12:
DOES YOUR
INFRASTRUCTURE
SUPPORT
ITERATIVE WORK?
PREVENTION #13:
DO TEAMS MANAGE
THE DEVELOPMENT
ENVIRONMENT?
HAVE YOU
INVESTED IN
AUTOMATED TEST
TOOLS?
PREVENTION #14:
TO LEARN MORE, CHECK OUT
DIRECTING THE AGILE
ORGANISATION
BY EVAN LEYBOURN
AVAILABLE AT AMAZON AND ALL
GOOD BOOK STORES
CL...
Autopsy of a Failed Agile Project
Autopsy of a Failed Agile Project
Upcoming SlideShare
Loading in …5
×

Autopsy of a Failed Agile Project

4,771 views

Published on

If you like the ideas raised in this presentation, don't forget to check out my latest book, Directing the Agile Organisation (http://theagiledirector.com/book).

Published in: Business, Technology
  • Article Marketing Submission is one of the best option for Getting Online Presences, Branding, Link Popularity and more things. http://fiverr.com/mcyrus/do-12-article-submission-service
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Autopsy of a Failed Agile Project

  1. EVAN LEYBOURN AUTOPSY OF A FAILED AGILE PROJECT
  2. Evan Leybourn Lean / Agile Business Leader and Author Melbourne, Australia @eleybourn http://theagiledirector.com
  3. Project 1: Business Intelligence Primary Cause of Failure: Customer Engagement
  4. SYMPTOM #1: POOR ENGAGEMENT AND COMMUNICATION
  5. SYMPTOM #2: NO TRUST BETWEEN BUSINESS &TEAM
  6. SYMPTOM #3: LACK OF SUBJECT MATTER EXPERTS
  7. POORLY MANAGED EXPECTATIONS SYMPTOM #4:
  8. MISUNDERSTANDING BUSINESS VALUE SYMPTOM #5:
  9. ‘A manufacturer is not through with his customer when a sale is completed. He has then only started with his customer.’ - Henry Ford, 1922
  10. PREVENTION #1: DO YOU HAVE THE RIGHT PRODUCT OWNER?
  11. PREVENTION #2: HAVE YOU TRAINED THE CUSTOMER & PRODUCT OWNER?
  12. PREVENTION #3: ARE THERE CLEAR AND AGREED EXPECTATIONS?
  13. Project 2: Telecommunications Primary Cause of Failure: Poor Planning
  14. SYMPTOM #6: CONFLICT BETWEEN CUSTOMER AND STRATEGIC WORK
  15. SYMPTOM #7: POORLY DEFINED PROJECT GOALS
  16. POORLY DEFINED SUCCESS CRITERIA SYMPTOM #8:
  17. ‘It is always wise to look ahead, but difficult to look further than you can see.’ - Winston Churchill, ~1960
  18. PREVENTION #4: IS THE SYSTEM FRAMEWORK AVAILABLE?
  19. PREVENTION #5: ARE THE GOALS AND END STATE CLEARLY DEFINED?
  20. PREVENTION #6: HAVE YOU PLANNED THE INITIAL ITERATIONS?
  21. Project 3: Government Primary Cause of Failure: The Team
  22. SYMPTOM #9: POOR AWARENESS OF THE WHY’S BEHIND AGILE
  23. SYMPTOM #10: CHRONICALLY UNDERSTAFFED
  24. SYMPTOM #11: MISSING REQUIRED SKILLS
  25. COMPETING PRIORITIES SYMPTOM #12:
  26. SYMPTOM #13: LOW TEAM MORALE, TRUST OR RESPECT
  27. SYMPTOM #14: POOR SUPPORT FROM EXTERNAL TEAMS (e.g. DBA)
  28. SYMPTOM #15: NOT DELIVERING VALUE IN EACH ITERATION
  29. ‘Treat your men as you would your own beloved sons. And they will follow you into the deepest valley.’ - Sun Tzu, ~6th Century BCE
  30. PREVENTION #7: ARE YOU RECRUITING FOR AN AGILE TEAM?
  31. HAVE YOU FOCUSED ON DEVELOPING TEAM CAPABILITY? PREVENTION #8:
  32. PREVENTION #9: CAN YOU POSTPONE STORIES NEEDING MISSING SKILLS?
  33. IS YOUR TEAM TRAINED IN AGILE? PREVENTION #10:
  34. Project 4: Information Management Primary Cause of Failure: Infrastructure
  35. UNDER- DEVELOPED ARCHITECTURE SYMPTOM #16:
  36. SYMPTOM #17: MISSING SUPPORT DOCUMENTATION
  37. SYMPTOM #18: UNSTABLE UPSTREAM SYSTEMS & DATA
  38. SYMPTOM #19: POOR TEST TOOLS AND DATA
  39. ‘Beautiful objects are wrought by study through effort, but ugly things are reaped automatically without toil.’ - Democritus, ~4th Century BCE
  40. HAVE YOU BUILT THE BASELINE INFRASTRUCTURE? PREVENTION #11:
  41. PREVENTION #12: DOES YOUR INFRASTRUCTURE SUPPORT ITERATIVE WORK?
  42. PREVENTION #13: DO TEAMS MANAGE THE DEVELOPMENT ENVIRONMENT?
  43. HAVE YOU INVESTED IN AUTOMATED TEST TOOLS? PREVENTION #14:
  44. TO LEARN MORE, CHECK OUT DIRECTING THE AGILE ORGANISATION BY EVAN LEYBOURN AVAILABLE AT AMAZON AND ALL GOOD BOOK STORES CLICK HERE TO DISCOVER MORE

×