The Enterprise DevOps Challenge
summary
Argues that successful enterprise DevOps uses iterative pilots, not big‑bang rollouts, and shows how a single user story can touch 120 people across teams, so mapping end‑to‑end cycle time is essential. Recommends building ephemeral infra and merging development and environment pipelines, creating a tiger team to negotiate temporary policy exceptions, and measuring outcomes like lead time to change and mean time to recovery. Gives a concrete migration path: pilot → create templates/wiki → scale trials, and cites the guinea‑worm example to show behavior change can drop millions to tens of cases.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 2:42Enterprise DevOps
- 3:45Challenges
- 5:19Guinea Worm
- 6:31What is a huge challenge
- 7:29Personal motivation
- 8:57Personal ability
- 9:38Trust
- 10:26Support
- 11:27No Structural Motivation
- 12:02Structural Ability
- 12:39Influence
- 15:29Change
- 16:11Influence Factors
- 17:45Transformations
- 18:55Middle Management
- 19:25Automation
- 19:43Behavior Organization
- 20:29Start with Pilots
- 21:19If this works
- 21:29Knowledge sharing
- 21:40We have no idea
- 25:42Application pilots
- 26:28Next steps
- 27:18Endtoend view
- 32:35Understand the bottleneck
- 35:36Look at the overall time
- 36:15Example
- 37:49Two parallel pipelines
- 38:36Policy
- 40:23Tiger Teams
- 43:12Exception Policy
- 46:26What is a Policy
- 48:42Measure the Opposite
- 51:51Good Metrics
- 53:12Mean Time Between Failures
- 56:44Red vs Green
- 58:06Time Between Red and Green
- 59:05Other Possible KPIs
related talks
01h 02mThe Enterprise DevOps Challenge
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
28mKeep Calm and DevOps in an Enterprise
27mInstilling DevOps Ways of Working in Large Enterprise...
45mOpening Keynote: The Enterprise DevOps Mind Trap
39mBringing DevOps into the Enterprise
29mHunting the DevOps Whale
47mOvercoming Obstacles to DevOps