The Structure of Software Revolutions
summary
Argues that Agile is the theory and DevOps/continuous delivery is the new paradigm, supported by tools and data: deployment frequency, lead time for changes, mean time to recover and change failure rate predict IT and financial performance per DORA/Puppet surveys. Cites Flickr deploying ~10x/day, a £12bn NHS permanent failure as a counterexample, and tooling trends (Jenkins, Octopus, cloud) that enable an continuous delivery pipeline. Claims leadership buy‑in, culture and automation are required and high performers show measurable business gains.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:50The Scientific Method
- 3:00Normal Science
- 4:06Anomaly
- 9:49The First Software Crisis
- 12:23Anomalies
- 18:15A Theory is not enough - Revolution requires achievements
- 21:31What is DevOps?
- 25:59The Andon Cord
- 30:07Data Gathering
- 32:00Establishing Cause and Effect with Performance Drivers
- 38:07Avoiding the alignment
- 42:51The Revolution Will Not Be Televised
related talks
31mThe Continuous Culture
34mDevOps: Next
32mDevOps as Driver of Organization-Wide Change
59mThe continuous culture
43mSoftware Eats Culture For Breakfast
37mWant to do the DevOps? Change Everything
48mUse DevOps to identify, embrace, and drive exponential Change
36mWhat do we know about continuous delivery – and what would we like to know