The Enterprise DevOps Challenge
summary
Enterprise DevOps succeeds by changing measurable behaviors not slogans: map a product value stream to find whether waiting time or work time is the bottleneck, run a small pilot/tiger team that automates policy checks into the pipeline, and swap broken metrics (build-count, coverage percent) for outcomes like lead time to change and measure mean time to recovery. Examples: fixing 700 broken tests re-enables nightly CI and sparks new tests; blue‑green and rolling deploys reduce recovery time; hardware and policy work can take months but the pilot learns what scales.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:10Learning comes from failure
- 1:56Roy Osherove
- 4:20Challenges
- 5:08The Reality
- 6:06The Core Skill
- 6:34Understanding Influence Forces
- 7:52Influencer
- 8:07Root Cause
- 9:09Root Behavior
- 11:44Factors of Influence
- 20:37Checklist
- 20:50Social Motivation
- 24:07Checklists
- 24:19Enterprise Challenges
- 29:23What is DevOps
- 31:40Everybody Champagne
- 31:54Management Whips
- 32:09Boil the Ocean
- 32:30Create Many Versions
- 33:50Pilot Team
- 35:19Bidirectional Support
- 35:40The Bubble
- 40:12The Policy
- 40:39The Ideal Pipeline
- 41:06Policy
- 41:37Tiger Team
- 44:14What do we change
- 45:19Value Stream
- 47:21Working Time
- 49:13Delivery Time
- 51:02Baseline
- 51:16Metrics
- 57:01DevOps Metrics
- 58:39AntiPatterns
- 58:59DevOps Values
related talks
01h 02mThe Enterprise DevOps Challenge
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
45mOpening Keynote: The Enterprise DevOps Mind Trap
34mYou only have to change one thing to do the DevOps
29mHunting the DevOps Whale
47mOvercoming Obstacles to DevOps
28mKeep Calm and DevOps in an Enterprise