Enabling a Continuous Deployment Mindset
summary
A single cross‑functional team modernizes a monolith used by ~1,000,000 users generating ~30,000,000 cases/year, moving from 1 deployment per quarter -> multiple commits per day by shipping an MVP with the strangler pattern, identical staging, automated unit/acceptance tests, automated smoke tests and feature toggles; deployments run via Jenkins + Slackbot and rollbacks are taught; the first production release finishes in a few hours, daily continuous deployment follows, and blameless timeline retrospectives drive safety improvements.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:30TEAM STRUCTURE
- 2:53LEGACY SYSTEM MODERNIZATION
- 4:07THE INITIAL MINDSET
- 5:39HOW WILL WE TACKLE THIS HUGE SYSTEM?
- 11:36WHERE IS THE MINDSET NOW?
- 14:10THE CURRENT MINDSET
- 16:39CREATE A "COLLECTIVE DEPLOYMENT" MINDSET
- 18:40THINKING SMALLER
- 21:09AND WHAT IF WE DO BREAK PRODUCTION?
- 22:48TIMELINE RETROSPECTIVES
- 25:02MAKE PAIN POINTS TRANSPARENT
- 25:50REACHING CONTINUOUS DEPLOYMENT
- 27:16THE CUSTOMER MINDSET
- 28:55THE CUSTOMER IS A PART OF THIS JOURNEY TOO
- 31:27KEY TAKEAWAYS
related talks
43mContinuously deploying a distributed monolith
49mThe road to continuous deployment: a case study
01h 01mA team's transition to Continuous Delivery
51mContinuous Deployment for a Billion Dollar Order System
41mShift Left, Shift Right and Improve the Centre
42mA Modern Development Culture for a Modern Development Process.
38mBuilding a high quality product
53mThe Road to Continuous Deployment: a Case Study
