I don't think these metrics mean what you think they mean!
summary
Argues that DORA metrics are lagging indicators and instead recommends leading signals: measure cycle time and inner cycles, limit WIP, track error budgets and change failure rate, and shorten lead time to change with automated CI/CD and testing plus modern observability. Gives concrete examples: some teams deploy 20–30 times a day (even hundreds), designate focused blocks like Tuesday noon–5 to reduce context switching, and treat improvements as measured experiments while investing in hands‑on enablement to lower MTTR.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:09Does being on your teams feel like being in the Pit of Despair?
- 2:59Four Key Metrics
- 3:43Deployment Frequency Ideation to Value
- 5:06Lead Time to Change
- 6:33Change Failure Rate
- 8:14Look at this Daily
- 10:09This isn't Rocket Science!
- 10:46That won't work here!
- 11:31There are risks in transformation!
- 12:49Creativity and a sense of joy
related talks
22mDORA Metrics: The Key to DevOps Excellence
44mEnhancing the Performance of Engineering Teams
14mSmarter #Testing for Better Speed & #Quality with DORA Metrics
47mCan We Measure Developer Productivity?
15mDev Team Metrics that Matter
21mHow to Increase Developer Productivity and Happiness
28mAccelerating Success: How to Optimize Value Delivery with DORA
06mDelivery Metrics: the good, the bad, and the totally ridiculous