A FAIRY TALE FROM THE LAND OF HANS CHRISTIAN ANDERSEN
summary
Interviews with 4 Danish companies and consultancy people report concrete tradeoffs: one product shop reaches 10 deploys per day and trusts developers to roll forward, another averages about one deploy per developer per day or one–two per week; many stop short of full continuous deployment with a human release button and preserve staging for long-running tests. Teams automate pipelines, break work into one-day tasks, and a high-performing company spends 30–40% refactoring time and uses focused retrospectives; dedicated infrastructure exists (one case has a tool team of 45).
AI-written summary · about
chapters (11)
- 0:00Start
- 2:51Extreme Programming
- 7:12Avoid Idle Time
- 12:15What Is Continuous Delivery
- 12:46What Is Continuous Deployment Continuous Deployment
- 13:58What Is Devops for Our Purpose
- 21:30Continuous Delivery Pipelines
- 23:00The Paradise Company
- 36:41Trip through Paradise
- 39:28Task Refactoring
- 48:12What Did You Learn Today
related talks
44mI Deploy On Fridays
47mContinuous Delivery Warstories
33m7 habits of a high performing team
46mContinuous Deployment Workflows
01h 01mA team's transition to Continuous Delivery
34mEnabling a Continuous Deployment Mindset
01h 01mI deploy on Fridays (and maybe you should too)
43mTo make mistakes is human. To auto-deploy it is DevOps.
