Continuous Delivery Delivers Value and So Do You: How to Get Budget, Build Your Case, and Be the Hero
summary
A concrete case shows a CD pilot that cuts DB change SLA from 72 hours to 15 minutes, moves DBAs out of tier‑one support with self-service DB changes, and achieves zero downtime while increasing deployment frequency. Measured gains include ~4.5% developer time saved across 3,500 devs (an initial headline of $29.9M saved, conservatively reported as $10.5M annual savings), pilot cost ≈10% of projected savings, and a 50% rejection rate driven down by automation.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:04Why CD deserves recognition
- 3:31CD adoption journey
- 7:06Stakeholder motivations
- 8:53Business case with metrics
- 13:09Business case breakdown
- 21:12Quantifying value
- 22:58Personal benefits of CD
- 25:04Q&A
related talks
29mMaking the Business Case for DevOps
47mContinuous Delivery Warstories
25mContinuous Delivery at Cisco IT
33mContinuous Delivery - What does good really look like?
11mLightning Talk: Continuous Delivery…except for Database Changes
26mHow Continuous Delivery and Lean Management Make your DevOps Amazeballs
30mHow a Business Exec Led Agile, Lead, CI/CD
34mDevOps: Next