Why We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
summary
Fourteen years of benchmarking 1,300 IT organizations claims that high performers combine rigor and discipline with two engineering practices: infrastructure checked into Version Control and automated one‑click environment creation. Concrete outcomes include cutting deployments from six hours to 45 minutes, Amazon’s mean rate of one deploy every 11.6 seconds (≈23,000/day), Netflix’s chaos‑monkey resilience experiments, a recommended 20% capacity for paying down technical debt, and an estimated $2.6 trillion annual value recapture.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:25rigor and discipline
- 8:50conflicting needs
- 10:12Alpha Hammond presentation
- 11:32Why we need DevOps
- 13:27The Three Ways
- 14:31Flow of Work
- 16:05Business Planning Sessions
- 17:23Lead Time
- 20:32Culture Hack
- 22:13Outcomes
- 29:06Defects
- 31:40Culture
- 36:47Collective Will
- 38:37One More Hack
- 40:33Why DevOps
- 43:12The Phoenix Project
related talks
45mDevOps: The Key to IT Performance
34mDevOps: Next
16mDevOps and the Bottom Line
31mThe Data Behind DevOps: What Does It Take To...
45mBuilding and Scaling High Performing Technology Organizations
27mDevOps Next
58mWhy Infosec Needs Rugged DevOps Now: A Study Of High Performing IT Organizations
05mInterview