Save 37% off PRO during our Black Friday Sale! »

Failing with Agility

Failing with Agility

If Agile methodologies are so great, why do we still fail over half the time?

D28499b3a2778ce8a1075c51f826cf01?s=128

Todd Kaufman

March 09, 2013
Tweet

Transcript

  1. Failing with Agility

  2. @toddkaufman @testdouble

  3. fail·ure /ˈfālyər/ Noun Lack of success.

  4. How do we define success?

  5. None
  6. Cost

  7. Cost Time

  8. Cost Time Scope

  9. Cost Time Scope Quality

  10. Cost Time Scope Quality

  11. None
  12. None
  13. Agile has made success nebulous

  14. ...but Agile is awesome!

  15. Now with 3x more success!

  16. 14%

  17. 42%

  18. None
  19. State of Agile

  20. 2011 Version One State of Agile Development

  21. 2012 Version One State of Agile Development

  22. Agile IS an improvement

  23. None
  24. Velocity!

  25. Frequent Releases

  26. Frequent Releases ... of shit

  27. Automated Tests

  28. None
  29. Your Team is WEAK

  30. Meet our Product Owners

  31. AWOL Product Owner

  32. PMs are not Agile Leaders

  33. Test Driven Developers

  34. Testers

  35. Agility and beyond!

  36. Project Success Agile Adoption vs

  37. None
  38. #1 Agile technique?

  39. None
  40. Certified Scrum Bag

  41. F*#K AGILE

  42. Find POSITIVE Deviance

  43. Earn TRUST

  44. Create LEARNING Environments

  45. DELIGHT Customers

  46. Treat Failure as FEEDBACK

  47. Redefine SUCCESS

  48. Thank you for the images: Clockwork Orange courtesy of Warner

    Brothers Starting Line courtesy of tableatny on flickr Execs courtesy of Mays Business School on flickr Half Bridge courtesy of daveemerson on flickr Game Over courtesy of jeff_golden on flickr House of Cards courtesy of furlined on flickr Poor Focus courtesy of leoglenn_g on flickr Motion courtesy of madlyinlovewithlife on flickr
  49. THANK YOU

  50. “Failure is simply the opportunity to begin again, this time

    more intelligently.” Henry Ford