60%: When Agile Fails

60%: When Agile Fails

As presented at Agile Tour London on 1st November 2013. This deck forms the backdrop to a product development tale that started in February 2013 and relates the lessons learned and pitfalls to avoid when using agile techniques in an area more familiar with traditional sequential delivery methods.

Ac5f436d1ac29c58b4f7756bf909ea94?s=128

Jon Whitaker

November 01, 2013
Tweet

Transcript

  1. 60% ! (when agile‘fails’) ! 1 !

  2. Introductions ! Jon Whitaker! @Jon_Whitaker! 2 !

  3. 3 !

  4. 60% ! (when agile‘fails’) ! 4 !

  5. Deliberate thinking ! 5 !

  6. Blink 
 Estimation! 6 !

  7. Surface risk early ! 7 !

  8. Oops!! 8 ! J J J J J J J

    J J J J J J J J J J J L L L L
  9. The neuroticism of Scrum ! 9 !

  10. What not to measure... ! (this is when agile ‘fails’)

    ! 10 !
  11. 60% ! (when agile succeeds) ! 11 !

  12. Three things: ! 1.  Trust your experience (and beware of

    cognitive bias)! 2.  Surface risk by testing your assumptions as early as possible (and keep doing so)! 3.  Measure the right things (quality and value) and know your constraints (scope, schedule and cost)! 12 !
  13. If you want more on any of this: ! “Thinking

    Fast and Slow”, Daniel Kahneman! “Blink Estimation”, Dan North (blog post)! “Agile Project Management”, Jim Highsmith! “Critical Chain”, Eliyahu M. Goldratt! 13 !
  14. 14 ! Canary Wharf Agile Forum ! ! www.meetup.com/canary-wharf-agile-forum!