Enable your team to do changes in production
summary
Claims that engineers can push changes straight to production after a multi-year program that rolled continuous delivery and cloud native practices through 180 teams at ING Bank and similar organizations. Shows concrete techniques: infrastructure as code, automated pipelines that build a fresh prod-like stack per release and tear it down, and audit hooks for compliance. Reports cycle time shrinking from months to minutes or hours, warns against copy‑paste Netflix patterns, and flags persistent problems around databases and organizational silos.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:40Topics
- 1:07Who is Mark
- 1:53Definitions
- 5:56Silos
- 7:10IT
- 8:45Application Delivery
- 10:22Build Team
- 11:08Deploy
- 12:25Delivery
- 14:26The Journey
- 15:03Triggers for changes
- 16:47Time to market
- 17:34The Golden Pyramid
- 21:55Netflix example
- 22:13Steal ideas
- 22:58Copy pasting
- 23:49Make teams departments
- 25:00Instant feedback loop
- 27:05How does it look like
- 29:05Summary
- 32:35Questions
- 36:15Testing
- 37:48Operating databases
related talks
34mYou only have to change one thing to do the DevOps
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
29mBanking on Continuous Delivery
25mContinuous Delivery and Testing in Production
54mBridging the Gap CICD Mind the Gap
25mGlobal Continuous Delivery in a Financial Organization
41mShift Left, Shift Right and Improve the Centre
01h 01mA team's transition to Continuous Delivery