The Rise and Fall of DevOps
summary
Argument asserts DevOps succeeds only if six interdependent links hold: mission, structure, ownership, platform, learning, trust; if one weakens delivery reverts from daily to multi‑day lead times. Examples include re‑architecting a monolith into domain teams plus a three‑person platform team (started when two product teams existed) that builds templated Jenkins patterns and treats the platform with the irresistible developer experience product mindset. Metrics like DORA are health signals not the mission. Distinction between platform as a service and platform as a ticket determines whether ownership actually works.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:04Defining DevOps
- 7:57Mission
- 10:57Structure
- 17:17Ownership
- 22:02Platform
- 25:09Learning
- 29:24Trust
related talks
11mDevOps Pitfalls, Beyond The Technology
17mDevOps Leadership in practice. True stories
22mDevOps vs Platform Engineering: Navigating the Path Ahead
05mDevOps Is Not a Department
42mWhy DevOps is not enough
48mNew barriers for DevOps adoption
46mBeyond DevOps: How and Why Companies Converge on Platform Models
45mOpening Keynote: The Enterprise DevOps Mind Trap