The metric in the middle
summary
Argues that one clear metric—release frequency—sits at the centre of judging agility, not sprawling dashboards from JIRA or PowerBI; measure how often working, tested software reaches users, then work backwards to fix CI/CD, approval gates or manual releases that block it. Warns against metric inflation (four times as many people measuring as change agents in one example) and recommends measure what matters and limit MIP: pick a small, contextual metric, improve it, remeasure, iterate.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:50Measuring agility challenge
- 3:35Pointy-haired boss metrics
- 6:01Metrics industry costs
- 10:15Agile metrics as tax
- 13:00Agility via release frequency
- 15:48CRISP assessment
- 18:12Team vs organizational agility
- 21:25Release frequency vs quality
- 25:03Golden metric: release frequency
- 27:11Measuring right things
- 28:58Avoid activity metrics
- 31:48Self-organization ownership
- 33:56Limit WIP for metrics
- 35:00Educating stakeholders
- 39:14Golden ticket of agile
- 41:22Overcoming leadership skepticism
- 44:12Q&A
related talks
52mMetrics Serving the Agile Performance of Your Transformation
26mMetrics-driven Data Architectures
32mHow to evaluate team effectiveness with a data first approach
44mThe cost of high-quality Agile metrics
48mInnerSource Metrics for Changing Engineering Culture and Driving Open-Source...
04mStartup Showcase: Metric Insights
19mThe Challenges of Product Analytics
28mStop querying tables: give AI governed metrics instead