The Data Behind DevOps: Becoming a High Performer
summary
State of DevOps reports from DORA (with Puppet and now Google) present concrete results: high performers show 46x more frequent deployments, 440x faster lead time from commit to deploy and 96x faster mean time to recover, with change failures about one fifth as likely and 50% higher market cap growth over three years. Architectural outcomes matter more than legacy vs greenfield tech. Lightweight or no change approval and short branch lifetimes (hours not days) correlate with better stability. Leadership measured by a five‑factor transformational model predicts technical and organizational performance.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:55Why did you do this
- 1:24Harvard Business Review
- 2:09IT Doesnt Matter
- 2:41Paper Cant Die in a Fire
- 3:04Technology matters
- 4:04Youre doing it wrong
- 4:54Flickr
- 5:16Lean Process
- 6:05Data
- 7:32What we see
- 9:11Why DevOps
- 10:57Maturity Models
- 11:47World of Warcraft Example
- 13:13The Challenge
- 16:55Technology Checklist
- 19:30Architecture
- 20:28Conways Law
- 21:03Leadership Matters
- 21:31Transformational Leadership
- 24:19DevOps Bingo
- 24:56Does it actually work
- 25:28Microsoft example
- 26:04NPS metric
- 26:31Change advisory boards
- 27:34Measure
- 28:16evangelize
- 28:56accelerate state of DevOps
- 29:22TLDR
related talks
31mThe Data Behind DevOps: What Does It Take To...
34mDevOps: Next
05mInterview
16mDevOps and the Bottom Line
27mDevOps Next
45mDevOps: The Key to IT Performance
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
45mBuilding and Scaling High Performing Technology Organizations