ADN Columbus 2013 - Visualizing Agility - Metrics That Matter

Transcript

1. 1.

   Visualizing  Agility   Metrics  That  Matter   Robert.Melchor@improvingenterprises.com  

2. 2.

   None
3. 3.

   Why  do  we  need  metrics?   How  do  we  decide

    which  metrics  to  use?   Which  metrics  should  we  avoid?   What  are  some  common  pitfalls?   What  are  some  powerful  but  seldom   used  Metrics?       Some  Questions  For  Today  
4. 4.

   None
5. 5.

   None
6. 6.

   Consequences  of  delayed  feedback  

7. 7.

   None
8. 8.

   None
9. 9.

   None
10. 10.

    10   Metrics: which Ones SHOULD WE Use?

11. 11.

    None
12. 12.

    Potential  Value     Seconds… Car Lengths Which  has  more

     value?  
13. 13.

    None
14. 14.

    Potential  Value     Lines of Code How  are  we

     performing?  
15. 15.

    ‘Easy’ TO MEASURE != Valuable

16. 16.

    Potential  Value     Features Accepted Lines of Code How

     are  we  performing?  
17. 17.

    Metrics  Effect  How  We  Behave  

18. 18.

    “Tell  me  how  you  will  measure  me  and  I  will

     tell   you  how  I  will  behave”  –  Eli  Goldratt   So…Be Careful What You Ask For
19. 19.

    Which  metrics  should  we  avoid?   19  

20. 20.

    Potential  Value     Average Velocity How  many  features  can

     we  complete  this   Sprint?  
21. 21.

    Be Careful What You Ask For

22. 22.

    Potential  For  Evil    

23. 23.

    Potential  for  Evil   Potential  Value     Features Accepted

    Lines of Code Average Velocity How  Well  Are  We  Performing?  
24. 24.

    What  are  some  Agile  metrics?   Potential  for  Evil  

      Potential  Value     Customer  Satisfaction   Value  Delivered   Work  Flow   Planning  Effectiveness   Code  Quality   Team  Collaboration  /  Interaction   Team  Empowerment  /  Accountability   Respect  /  Trust   ?
25. 25.

    None
26. 26.

    What  are  some  common  pitfalls?  

27. 27.

    Page    27   Project Goals Cost  to  respond  

    $   Cost  to  respond   $$$$$   “…We  have  come  to  value…   Responding  to  Change”  
28. 28.

    None
29. 29.

    Metrics:  Make  Em  Visible!     29   0%  

    20%   40%   60%   80%   100%   120%   140%   160%   180%   200%   1   2   3   4   5   6   Iteration  Productivity   Points  Accepted  vs  Points  Planned   The  Buffet  Rule:    “Take  all  you   want,  but  eat  all  you  take”  
30. 30.

    Utilizing  Storyboard  

31. 31.

    What are some powerful (but seldom used) metrics?

32. 32.

    Agile  Assessments…  

33. 33.

    Consider  ‘Project  Sliders’  

34. 34.

    Lead  Time   Cycle  Time   WIP   Remaining  to

     be  done   Scope  Increase   How  is  our  throughput?  
35. 35.

    How  much  time  do  we   spend  waiting?   “Agile

     is  the  art  of  eliminating  delay”     –  Alan  Shalloway  
36. 36.

        Process  Cycle  Efficiency  (PCE)   Page    36

      %  Time   Effort   Delay   =    100%  PCE  (  zero  delay  )     6  days  effort   6  days  duration   Effort  =     Duration  
37. 37.

    Process  Cycle  Efficiency  (PCE)   Page    37   %

     Time   Effort   Delay   Duration  =  14  days     =  43%  PCE   6  days  effort   14  days  duration   Effort  =  6   days  
38. 38.

    How’s  our  code  quality?   http://www.crap4j.org   http://www.ndepend.com  

39. 39.

    What  question  are  we  trying  to  answer?   What’s  the

     goal  (target  condition)?   Who  is  the  target  audience?   What’s  the  relative  value  of  the  metric?   What  undesirable  behavior  might  this  drive?   How  will  people  try  to  game  it?     In  deciding  which  metric  to  use   Ask…  
40. 40.

    1.  Make  them  transparent   2.  Make  them  visible  

    3.  Show  a  trend   4.  Make  them  relevant  &  timely   5.  Have  a  purpose   http://blogs.versionone.com/agile_management/2013/06/21/five-­‐simple-­‐guidelines-­‐to-­‐agile-­‐metric-­‐bliss /       Agile  Metric  Suggestions  
41. 41.

    Robert  J.  Melchor   Robert.Melchor@improvingenterprises.com   www.linkedin.com