Obstacles & Patterns To Maximize Flow in IT Operations
summary
Lists 11 patterns that convert strategy into repeatable ops: value stream mapping to visualize handoffs and measure cycle times, standard work with execution times, and Kanban boards (not just Jira) to manage flow. Prescribes small-batch deploys, idempotent deploy tools, automated security scans, A3/PDCA for Kaizen, and stop-at-source quality (jidoka) with gemba walks and kata practice. Calls for shared why and trusting relationships, ruthless removal of vision blockers, and continuous measurement of deploy speed, stability and customer impact.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:13Flow
- 3:14DevOps Flow
- 4:01Good vs Service
- 5:05Systems Thinking
- 6:27Interaction
- 9:26Why
- 10:39Trust
- 13:40Customer Focus
- 14:30Fight the Vision
- 15:00Value Stream Mapping
- 17:16Standardise Your Work
- 18:27Conbond
- 20:01Muda
- 22:14Kaizen
- 25:50Efficiency
- 26:25Quality at the Source
- 28:28Go and See
- 29:24Practice Teach
- 30:59Review
- 32:34Lean
- 34:48Cross Team Sites
- 36:26Ops People
- 38:34Lean vs Service
- 40:07History of Kaizen
related talks
18mDesign Patterns For Efficient DevOps Processes
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
47mMap and Measure your way to Performance
33mTaming The Chaos: After The Quick Wins
22m4 Maps of DevOps
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
28mThe DevOps Pipeline