Slides from Agile Metrics discussion at Agile:MK, March 2019

1. Agile Metrics
Agile:MK – March 2019

2. Firstly…
Thanks again to WorkForce

3. Some ideas to consider
• Cost of metrics
• Proxy metrics
• Predictive or Retrospective metrics
• What gets measured gets managed

4. Tonight’s Goal (perfect version)
Decide the definitive small set of
cheaply collected metrics that
perfectly correlate to success

5. Tonight’s Goal (more probable version)
Understand pros and cons of
multiple metrics that can help us
and take away some things to try

6. Question
Who is using these metrics and
what are they trying to achieve?

7. Question
What metrics can we gather?
• Are they cheap/expensive
• Are they predictive or retrospective?
• Do they directly measure what we care
about, or are they a proxy?

8. Metrics we can gather
Metric C/E P/R D/P Metric C/E P/R D/P
Cheap / Expensive
Predictive / Retroactive
Direct / Proxyo

9. Question
What are the pros and cons of
these metrics?
• Are some just bad?
• Are some (almost) always good?

11. Some Metrics
• Lines of code
• Function points
• Bugs
• Story point velocity
• Throughput
• Cycle time
• Business value delivered
• Customer satisfaction
• Up time
• Team happiness
• Technical debt

12. Four key metrics:
• Delivery lead time
• Deployment frequency
• Time to restore service
• Change fail rate

13. • If you can find a metric or set of
metrics that perfectly track what
makes you successful, then use
them
• If you have a set that perfectly
track part of what makes you
successful, then be very careful

14. Metrics we can gather
Metric C/E P/R D/P