Just Ship It!
summary
Claims that continuous deployment reduces sprint chaos by forcing safe partial releases and automation backed by monitoring and quality gates. Cites DORA growth from ~7% to ~20% elite daily deployers and a target change‑failure rate of 0–15%. Describes a built example: add DB column, ship backend calc to prod, use feature toggles to expose UI later — production runs on real data as an involuntary beta and it catches edge cases. Requires infra like blue/green deployments, monitoring, WIP limits and cross‑skill training; two projects deploy daily with ~2% failure.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:06Continuous deployment vs delivery
- 2:32DORA elite performers
- 4:40Benefits of immediate deployments
- 6:05Sprint-based deployment problems
- 9:58Sprint-end deployment chaos
- 11:02WIP limits to prevent bottlenecks
- 14:11Full agile with continuous deployment
- 15:34Myths about continuous deployment
- 16:15Safe database/backend deployments
- 18:25Testing tax calculation in production
- 20:33Feature toggles and gradual rollouts
- 21:55Risks of big-bang deployments
- 24:42Steps to start continuous deployment
- 25:45Infrastructure for live deployments
- 26:49Canary releases and reliability
- 27:53Monitoring and quality gates
- 29:17Three pillars for successful CD
- 30:00Team growth and training
- 31:45Metrics and failure rates
- 32:46Management support for automation
- 34:32CD trends and UX standard
- 35:57Speed versus user frustration
- 36:37Driving transformation
- 37:20Continuous deployment as normal
related talks
40mContinuous Delivery Anti-Patterns
33m7 habits of a high performing team
36mWhat do we know about continuous delivery – and what would we like to know
59mThe continuous culture
17mShip, Sense, and Respond: A Culture of Continuous Learning
32mHow Your Deployment Strategy Influences How People Code
55mContinuously Delivering Continuous Delivery
30m10 Ways to Improve How You Ship Software