From Gut Feel to Evidence: What DORA Metrics Actually Tell Us
summary
Shows how DORA metrics plus a Process Behavior Chart turn opinions into testable hypotheses: measure one outcome, pick the highest‑leverage change, verify against variation. Concrete results include pair programming dropping median change lead time from ~10 hours to ~3 hours — a 70% improvement with deployment frequency up and quality stable — and a monolith migration that first increases lead time from 48→80→17 hours until a policy approval is removed, proving the intervention rather than the activity matters.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:17Gut feeling to evidence
- 3:02Measuring real change
- 6:12Why DORA metrics
- 9:22Choosing capability
- 10:47Process behavior charts
- 12:51Pair programming test
- 19:57Legacy migration outcomes
- 23:08Start small verify
- 24:12Summary
related talks
23mOptimizing Delivery with DORA Metrics: How We Prepared and Where to Start
29mA DORA Metrics Adventure in Deciphering Engineering Changes
28mAccelerating Success: How to Optimize Value Delivery with DORA
22mDORA Metrics: The Key to DevOps Excellence
30mIntroducing DORA Core: Durable research insights for technical practitioners
19mAccelerating Code Quality with DORA Metrics
25mTroubleshooting at Scale: What DORA Metrics Miss
22mPanel Discussion: Let's Improve - Leverage DORA to Im...