DevOps Kaizen: Empowering Teams to find and fix their own Problems
summary
Claims a repeatable Kaizen system that combines value stream mapping with Lean waste analysis and improvement kata, tracks four end-to-end metrics (lead time, processing time, MTTD, MTTR, scrap rate), and turns findings into A3/storyboard projects that leaders fund and protect (about 15–20% of capacity). Examples: a financial org cuts planning lead time from ~17 weeks by standard catalogs and ops earlier involvement; one team shifts test data setup from six weeks to six hours via self-service and environment verification.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 3:37Blameless postmortems
- 7:14Silos
- 9:37Complexity
- 10:58The Black Box
- 14:47Continuous Improvement
- 17:00Kaizen
- 18:43Lean Techniques
- 25:01Value Streams
- 25:53Flow of Work
- 27:04Factory View
- 28:04Black Pen
- 29:54Common DevOps Patterns
- 30:39countermeasures
- 31:37storyboards
- 32:35planning process
- 33:46early operations involvement
- 35:56environment verification tests
- 36:30deployment
- 36:59storyboard
- 40:52coaching pattern
- 41:29transformation plan
- 41:59retrospective view
- 45:31oversight
- 47:18motivation
- 47:34inspiration
- 48:18follow through
- 48:45overlay
- 49:39recap
- 51:11contact me
- 51:49two ways to do it
related talks
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
27mDevOps Champions: Leading the Transformation
29mDevOps Transformation at Scale
09mexplains DevOps Culture
15mOptimizing the engineering value stream
54mValue Streams, Quality Engineering And You
41mPlatform teams: Applying Lean practices to reduce their Operational workload
30mA Story of DevOps Transformations