Deploying to Production on Friday
summary
The talk addresses the recurring belief that deployments should not happen on Fridays and argues for disciplined change management for large-scale releases. It explains why formalizing at least parts of the deployment process and coordinating across teams improves safety, and rejects the idea that pushing to production will inevitably work out without proper controls.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25Managing production changes
- 4:18Change deployment process
- 6:25Risk assessment and sensitivity
- 13:16Risk factors
- 20:23Risk measurement and methodology
- 23:13Risk examples and tests
- 27:32Risk reduction and rollback plan
- 33:16Testing and environments
- 36:54Change failure and impact
- 39:44Fast track and emergency path
- 42:54Summary and Q&A
related talks
44mI Deploy On Fridays
01h 01mI deploy on Fridays (and maybe you should too)
47mI Deploy on Fridays (And Maybe You Should Too)
38mFearless Deploys on Friday Evening. Wait; what?!
31mFireside Chat: Continuous Deployment
26mThe emotional chaos of deploying code
46mContinuous Deployment Workflows
31mReducing the fear of go-live