New barriers for DevOps adoption
summary
Argues that the blockers are now organizational not just skills or tools: goals, dogma, technology limits, culture and over‑optimism. Gives concrete failures — Jenkins wiped with pipelines not in source control that cost weeks to recover, 1,500 bespoke CI configs, and examples of forcing Siebel into Docker. Cites cloud compliance dropping from 67% to 22% on key APIs. Recommends self-service platform teams, measure with value‑stream mapping, log timestamps to track the optimal batch size, and stop trusting a return code zero as proof of success.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 3:44Why we still solve old problems
- 7:03Setting realistic transformation goals
- 11:10Optimal batch size in IT
- 13:51Avoiding DevOps dogma
- 17:21Centralized DevOps platform teams
- 21:04Continuous delivery as a journey
- 22:10Choosing enabling technologies
- 26:12Culture and organizational change
- 34:23Bridging the DevOps understanding gap
- 36:35The danger of techno-optimism
- 40:01No end-state in DevOps
- 41:26Q&A session
related talks
27mThe curious case of the DevOps engineer and other things ...
47mOvercoming Obstacles to DevOps
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
45mOpening Keynote: The Enterprise DevOps Mind Trap
30mA Story of DevOps Transformations
30mAdopting DevOps? You are aiming at the wrong target!
34mDevOps Transformation from the C-Level point of view
37mWant to do the DevOps? Change Everything