DevOps Kaizen Practical Steps to Start & Sustain a Transformation
summary
Applies Kaizen to DevOps at enterprise scale with specific practices: track service-delivery metrics (lead time vs processing time, mean time to detect/repair), run value stream retrospectives to map flow, capture blockers and create short actionable countermeasures on A3 storyboards. Example client: feature delivery takes 40 weeks with 17 weeks planning and 71% requirements change; two integration environments cause ~50% environment failures and 80–90% bad test data. Fixes include self-service test data and verification tests and cut large amounts of cycle time. Executive role is clearing blockers, funding and follow‑through.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:57RunDeck
- 1:31Improvement
- 3:51Traditional Visibility
- 4:29Complex Systems
- 5:20What do we do
- 6:11Delivering the Big Bang
- 6:53Big Bang Dreams
- 7:10How do you teach an organization to fix itself
- 7:47Continuous Improvement
- 9:10DevOps Kaizen
- 10:43Right Service Delivery Metrics
- 12:31Horizontal Thinking
- 13:24Value Stream Mapping
- 14:33Lean Inspiration
- 15:00Flow of Value
- 15:24Countermeasures
- 16:07Sales Technique
- 16:25Fixing the Flow
- 17:04Big Planning Cycles
- 17:56Rubberstamping
- 18:44Integration Environments
- 19:26Service Verification
- 20:24Storyboards
- 21:08Sales Pitch
- 21:35Value Stream Map
- 21:54Making Progress
- 22:05Learning
- 22:33What are they there to do
- 22:48They are there to clear obstacles
- 23:00Get them inspired
- 24:37Recap
related talks
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems
29mDevOps Transformation at Scale
49m5 Steps to a DevOps Transformation
01h 02mThe Enterprise DevOps Challenge
47mOvercoming Obstacles to DevOps
27mDevOps Champions: Leading the Transformation
45mDevOps Transformation — Breaking Down Walls
30mA Story of DevOps Transformations