Dev Team Metrics that Matter
summary
Argues that the right outcome-first metrics are DORA’s cycle time and change failure rate and shows concrete effects: analysis of customer data (3.9 million comments, ~25k developers) finds PRs under 200 changes merge much faster and raise deployment frequency. Describes tools and fixes that work: CI/CD plus Slack bots for one-click approves, an AI estimated time to review, and a Git-stream YAML rules engine for automated merges that cuts pickup/review idle time.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:08Dev Team Metrics That Matter
- 7:03Dora Metrics Devops Research and Assessment Metrics
- 8:06Cycle Time
- 10:18Pickup Time
- 10:34Review Time
- 12:08Speed Deployment Frequency
- 13:14Cfr Change Failure Rate
- 21:26Common Delivery Process
- 24:52Ci Cd
- 25:44Idle Time
- 28:43Continuous Merge
- 29:48Pull Request Life Cycle
- 33:57Estimated Time To Review
- 34:45Git Stream Solution
related talks
22mDev Team Metrics that Matter
15mDev Team Metrics that Matter
37mCI/CD Observability, Metrics and DORA: Shifting Left and Cleaning Up!
44mEnhancing the Performance of Engineering Teams
22mDORA Metrics: The Key to DevOps Excellence
19mAccelerating Code Quality with DORA Metrics
25mTroubleshooting at Scale: What DORA Metrics Miss
30mDevEx and Productivity Metrics on Backstage - Do's and Don'ts