Agile Metrics

Metrics are so often misused that they tend to become more of a hinderence than a help. The numbers aren't at fault though, how can we leverage the metrics to improve visibility without obsessing over them?

Transcript

1. Metrics That Matter Todd Kaufman Saturday, March 10, 12
2. Metrics That Matter Todd Kaufman Saturday, March 10, 12
3. How to stop abusing yourself and others with Metrics Todd Kaufman Saturday, March 10, 12
4. Metrics are ______ to a software development team? Saturday, March 10, 12
5. How does your boss, product owner, or client answer that question? Saturday, March 10, 12
6. Lights On! Saturday, March 10, 12
7. Defects are up! Saturday, March 10, 12
8. Velocity is down! Saturday, March 10, 12
9. We’re tracking a month late! Saturday, March 10, 12
10. Saturday, March 10, 12
11. An example to illustrate... Saturday, March 10, 12
12. Team is achieving 20 pts per iteration Saturday, March 10, 12
13. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Saturday, March 10, 12
14. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Saturday, March 10, 12
15. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Saturday, March 10, 12
16. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Team hits 7 pts next iteration Saturday, March 10, 12
17. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Team hits 7 pts next iteration Team hits 3 pts next iteration Saturday, March 10, 12
18. Team is achieving 20 pts per iteration Release is planned at 4 iterations out Sprint backlog is estimated at 70 pts left Team hits 17 pts next iteration Team hits 7 pts next iteration Team hits 3 pts next iteration Team hits 6 pts last iteration Saturday, March 10, 12
19. Pressure Causes Fractures Saturday, March 10, 12
20. Once these cracks have developed... Saturday, March 10, 12
21. They cannot be easily mended Saturday, March 10, 12
22. Saturday, March 10, 12
23. sadometricism Saturday, March 10, 12
24. sadometricism The gratification of oneself through metrics to the point of pain for the individual and those around them. Saturday, March 10, 12
25. Can we maintain visibility without obsession? Saturday, March 10, 12
26. Yes! If we just use some common sense Saturday, March 10, 12
27. Protip 1: Only use metrics when answering a question Saturday, March 10, 12
28. Protip 2: Understand your audience Saturday, March 10, 12
29. Protip 3: Empower your team Saturday, March 10, 12
30. Protip 4: Pick the best metric for the job Saturday, March 10, 12
31. Protip 5: Favor metrics that are difficult to game Saturday, March 10, 12
32. From Misused to Rarely Used... Saturday, March 10, 12
33. Velocity! Saturday, March 10, 12
34. How could velocity possibly be misused? Saturday, March 10, 12
35. Velocity is down! Saturday, March 10, 12
36. Velocity is up! Saturday, March 10, 12
37. Team or individual comparison Saturday, March 10, 12
38. Velocity isn’t all bad Saturday, March 10, 12
39. Story Points Remaining Saturday, March 10, 12
40. Precision implies Accuracy Saturday, March 10, 12
41. Assumes knowledge of the unknown Saturday, March 10, 12
42. Stories are like rabbits Saturday, March 10, 12
43. BTW, how did you estimate all these stories ? Saturday, March 10, 12
44. Saturday, March 10, 12
45. If you need a swag, base it off epics, features, or stories and assume change Saturday, March 10, 12
46. Favor burnups if you need graphs Saturday, March 10, 12
47. Change Introduced !20$ 0$ 20$ 40$ 60$ 80$ 100$ Itera.on$1$ Itera.on$2$ Itera.on$3$ Itera.on$4$ Itera.on$5$ Itera.on$6$ Itera.on$7$ Itera.on$8$ Itera.on$9$ Itera.on$10$ Itera.on$11$ Itera.on$12$ Itera.on$13$ Cumula.ve$ Remaining$ Saturday, March 10, 12
48. We all have deep scars from waterfall projects Saturday, March 10, 12
49. Resistance to change Saturday, March 10, 12
50. What question does this metric answer? Saturday, March 10, 12
51. Contracting on this rarely works Saturday, March 10, 12
52. Saturday, March 10, 12
53. Lines of Code Saturday, March 10, 12
54. Code Coverage Saturday, March 10, 12
55. Cyclomatic Complexity Saturday, March 10, 12
56. Cyclomatic Complexity + Code Coverage Saturday, March 10, 12
57. Broken Builds Saturday, March 10, 12
58. Defects Saturday, March 10, 12
59. Cycle Time Saturday, March 10, 12
60. cycle time > velocity when... Saturday, March 10, 12
61. Cards are all relatively equal sized Saturday, March 10, 12
62. Team is mature enough to resist commitments and estimation Saturday, March 10, 12
63. Past performance does not guarantee future results Saturday, March 10, 12
64. Team Happiness Saturday, March 10, 12
65. “Negativity kills innovation” - Venkat S. Saturday, March 10, 12
66. Difficult to quantify Saturday, March 10, 12
67. Saturday, March 10, 12
68. Business Value Earned Saturday, March 10, 12
69. Which means more to your business? $ earned story points delivered Saturday, March 10, 12
70. C*Os understand and speak this language Saturday, March 10, 12
71. Contracting by this means true alignment Saturday, March 10, 12
72. Running Tested Features Saturday, March 10, 12
73. “Nearly every metric can be perverted, since up- and down-ticks in the metric can come from good or bad causes. Teams driven by metrics often game the metrics rather than deliver useful software. Ask the team to deliver and measure Running Tested Features, week in and week out, over the course of the entire project. Keeping this single metric looking good demands that a team become both agile and productive." Saturday, March 10, 12
74. Features Used Saturday, March 10, 12
75. How much would you pay to know what features your customers used and what they didn’t? Saturday, March 10, 12
76. Validated Learning Saturday, March 10, 12
77. Validated learning is the process of demonstrating empirically that a team has discovered valuable truths about a startup’s present and future business prospects. Eric Ries - The Lean Startup Saturday, March 10, 12
78. Talk to your Customers! Saturday, March 10, 12
79. So what have we learned? Saturday, March 10, 12
80. STOP the abuse! Saturday, March 10, 12
81. Saturday, March 10, 12
82. Metrics are information radiators Saturday, March 10, 12
83. Metrics are information radiators Leverage them Saturday, March 10, 12
84. Metrics are information radiators Leverage them Only when solving a problem Saturday, March 10, 12
85. Metrics are information radiators Leverage them Only when solving a problem That is worth solving Saturday, March 10, 12
86. “Not everything that counts can be counted, and not everything that can be counted counts.” Saturday, March 10, 12
87. Thank you! Saturday, March 10, 12
88. @toddkaufman toddkaufman@gmail.com Saturday, March 10, 12