If you don't know how to measure what you want, you'll end up wanting what you can measure. Most often the thing you want to know isn't easily quantifiable, and common proxy metrics are usually poorly correlated with the information you actually need. Measuring the wrong things is worse than nothing—a toxic metric can damage your teams' performance.
With the right data, you can change the conversation. Tell your team's authentic story to management, your customers, and beyond. Step away from dangerous metrics that punish unfairly. Quit wasting time with metrics that are easily gamed. Instead, choose effective metrics to get everyone on the same page about what's important.
Whether you're the measurer or the measuree, in this session, you'll learn not just which metrics work, but why and how. Our examples will focus mainly on team, project, and program metrics, with theoretical guidance to inform all kinds of measures including portfolio and organization. Understand the difference between true metrics and proxy metrics, and good proxies and evil ones. Discover a framework for evaluating any metric, a Hall of Shame covering some of the worst most popular benchmarks, and one true guide to point you to the very best metrics of all. See some great examples of visualization that make metrics sing, and leave with several concrete measures you can begin tracking as soon as you get back to your desk.
Learning Outcomes:
* Difference between true and proxy metrics
* Characteristics of good metrics
* Examples of common bad metrics and why you should stop using them
* Great metrics, including counterintuitive ones, that correlate to the performance you want to influence
* Some examples of measurements where qualitative, not quantitative, works best
3. one metric to rule them all
effectively measure your teams without subjugating them
Cheryl Hammond
Technical Strategist, Northwest Cadence
cheryl.hammond@nwcadence.com @bsktcase
4. agreements and asks
@bsktcase #Agile2015 #onemetric
Tweet your feedback and questions during and after and whenever
http://sched.co/36PX
Submit your feedback please please please
6. me
Cheryl Hammond
16+ years’ experience in software
development, team leadership, and
organizational transformation
Passionate about agile, lean, and
making software delivery humane;
not afraid to look silly doing it
From/in Seattle, the other Washington
College (university) recruiter; traveler;
bolonka lover; genealogist; feminist
8. “Managers who don’t know how
to measure what they want
settle for wanting what they can measure.”
Russell L. Ackoff
http://en.wikiquote.org/wiki/Russell_L._Ackoff
t5#x#7V8 o`N 25^.1 z5yN 9yN.1`N t`ViE7MË o1D 3nVÍ y1Dp.81F;jL e6N y1Dpx%P o1D 3nVÍ z5# t`ViE7MË-
11. “If you give a manager a numerical target,
[s]he’ll make it even if [s]he has to
destroy the company in the process.”
W. Edwards Deming
eB nÍyN xr%È `C t5#x#6V `C 5t&7VzGj# 17Ex1F=.8.9`V.j° tzDÊ 1G r$5$ eB 8.9Ë 9iE 1`N 2iV17nNÍ @ zqNp5#Ì 5% @ q7zNiV;-
20. “Any observed statistical regularity
will tend to collapse once pressure is placed
upon it for control purposes.”
Goodhart's Law
http://en.wikipedia.org/wiki/Goodhart's_law
5#Ì wH87Vr2R 811DiT1zGj# 7xRj&7E1GÎ yj%° 12RP 1`N zj^°qD8Ê zNÊp q7iV;7MË iT qjzD2R qJ5^ 1G e6N z1Np7j^ q7MqiNiV-
25. lean and agile metrics are simple
Metrics aren’t free
Time to collect
Time to tabulate
Time to pretty up
Tools
Morale
Be sure the benefit justifies the cost!
28. time to feedback metrics
True
Mean time to stakeholder feedback
Lead time
Cycle time
Proxy
Wait time
Touch time
Work in process (WIP)
Queue length
MTTR⁴
Realize, Recover, Repair, Remediate
Code coverage
Escaped bug rate
34. agreements and asks
@bsktcase #Agile2015 #onemetric
Tweet your feedback and questions during and after and whenever
http://sched.co/36PX
Submit your feedback please please please