A DORA Metrics Adventure in Deciphering Engineering Changes
summary
Practical method using DORA metrics plus git and Jira signals to answer whether a change is needed, how widely it’s adopted, whether it speeds delivery, and what it breaks. Claims: track Need, Adoption, Impact, Risk; measure adoption with PR counts (example comparisons showed adoption anywhere from a third of the org to near 90%), measure impact with lead time for change and deploy frequency, measure risk with PR size and review bottlenecks. Example dashboard surfaces co‑pilot PRs that are larger and increase review time so the change can be managed.
AI-written summary · about
chapters (10)
- 0:00DORA Metrics intro
- 1:46Engineering change challenges
- 6:47Metrics for change navigation
- 9:13DORA metrics evolution
- 12:03Dev productivity vs business
- 13:50Case study: new tech with DORA
- 19:09Case study: firefighting with data
- 21:38Pitfalls in engineering metrics
- 25:29Engineering and business goals
- 26:18Q&A
related talks
25mFrom Gut Feel to Evidence: What DORA Metrics Actually Tell Us
22mDORA Metrics: The Key to DevOps Excellence
22mDev Team Metrics that Matter
22mPanel Discussion: Let's Improve - Leverage DORA to Im...
15mDev Team Metrics that Matter
31mThe four key metrics, Unleashed!
28mAccelerating Success: How to Optimize Value Delivery with DORA
19mAccelerating Code Quality with DORA Metrics