From bi-annual to fortnightly releases in 4 months for 15 teams and one monolith
summary
15 teams sharing a 20‑year Java monolith move from bi‑annual to fortnightly releases in four months by using Improvement Kata, Value Stream Mapping and Theory of Constraints; they measure lead time and failure rate, build a simple deployment pipeline that runs tests (initial lead time 8h, 70% failure rate), split stable/unstable tests, recreate test DBs and add dashboards. Result: pipeline lead time falls to 2–4h, releases every two weeks like clockwork, Continuous Delivery achieved though full Continuous Integration remains unmet.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 1:47Project background and goals
- 8:15Why maturity models fail
- 11:04Core team setup and approach
- 13:12Continuous delivery fundamentals
- 17:25Improvement Kata explained
- 19:54Value stream mapping workshop
- 24:09Theory of constraints applied
- 27:40First experiment deployment pipeline
- 31:54Fear conversations and challenges
- 33:16Complexity fear and branching strategy
- 38:20Deadline fear and manual overrules
- 39:46Reputation fear and test stability
- 41:36Fortnightly releases achieved
- 42:42Continuous delivery vs integration
- 44:27Key success factors and lessons
- 46:54Conclusion and Q&A
related talks
35mTaming a beast
26mDevOps and Lean in Legacy Environments
32mClimbing the Mountain of CI/CD: A Tester’s Tale
01h 01mA team's transition to Continuous Delivery
34mEnabling a Continuous Deployment Mindset
28mClimbing the Mountain of CI/CD: A Tester’s Tale
41mShift Left, Shift Right and Improve the Centre
47mContinuous Delivery Warstories