Continuous Delivery, high-performing engineering teams, and the Holy Grail
summary
Analysis of 15 million CircleCI workflows correlates four CI/CD benchmarks — duration, mean time to resolve, success rate, throughput — with actionable targets and tradeoffs. Median workflow completes in 3.3 minutes, 25% under one minute and 75% under nine; top 5% run ~7 times/day while median runs ~1.54. Recommended practices include fix broken builds in <60 minutes and aiming for default branch ≈77% success with a 90% target, plus using a Platform Team to raise test quality and throughput.
AI-written summary · about
chapters (9)
- 0:00Continuous delivery intro
- 2:52Defining continuous delivery
- 5:39Software delivery report
- 7:06CI/CD pipeline duration
- 12:43Time to fix builds
- 16:33Build success rate
- 19:43Team performance metrics
- 23:56Optimizing team metrics
- 24:58Q&A
related talks
33mHigh performing engineering teams and the Holy Grail
36mDevOps Performance From a Different Dataset: What 30M Workflows Reveal
48mDemystifying CI/CD
24mCI/CD Best Practices to Deliver Software Faster
27mThe Need for Speed (in your CI/CD setup)
32mPractical Tips & Tricks for CI/CD Success
17mCI/CD - Build/Deploy Automation
50mFast Doesn’t Mean Fragile: Delivering AI-Powered Software at Scale