Continuous Delivery and the Theory of Constraints
summary
Explains applying the Theory of Constraints and the Five Focusing Steps to the build→test→ops value stream, identifying production/release testing or a single overworked release manager as typical constraints. Shows concrete results: a deployment pipeline used for 70 apps, build time cut from 1.5 hours to 3 minutes, release time to ~1 hour, and an experiment that shifts interval from 21 to 14 days by changing release notes, cadence and staffing rather than rebuilding everything. Recommends exploit, subordinate, elevate, then repeat.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:47Continuous Delivery
- 4:55The Deming Cycle
- 8:54Lead Time
- 9:24Technology Capabilities
- 11:06Organizational Capabilities
- 11:35Burnout
- 12:33Lean Enterprise
- 13:17Accelerate
- 14:37My book
- 16:04Deployment throughput indicator
- 17:04Lead time vs interval
- 18:39Theory of Constraints
- 19:59NonConstraints
- 20:43Constraints
- 27:33The Theory of Constraints
- 31:46Using Theory of Constraints
- 34:22The Challenge
- 38:13Organizational Changes
- 40:00Deployment Through Per Indicator
- 40:35Free Changes
- 41:11Key Learning
- 42:29Takeaways
- 44:03Outtakes
related talks
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
43mSoftware Engineering Management at Scale with the Theory of Constraints
33mContinuous Delivery - What does good really look like?
59mThe continuous culture
51mBetter software, faster: principles of Continuous Delivery and DevOps
32mContinuous Delivery Sounds Great But It Won’t Work Here
41mContinuous delivery in 10 easy mistakes
40mDevOps, 12 Factor, and Open Source