Turning continuous delivery into competitive business advantage
summary
Continuous delivery creates business effects beyond engineering: a Microsoft study shows 2/3 of ideas are bad so faster shipping needs better validation. Real examples: a PayPal UI rollout briefly hides £5,000 across accounts; Tesla owners expect features tied to specific hardware and start petitions; GitHub/Dropbox win by selling capacity not features. The concrete fix is to decouple deployment and release and build true multiversion support (routing, data migration, versioned requests) so rollouts target cohorts and avoid breaking marketing or support.
AI-written summary · about
chapters (9)
- 0:00Continuous delivery backfires
- 3:36Who controls delivery
- 8:32Hidden costs of updates
- 15:37Delivery disrupts sales
- 22:16When delivery harms business
- 25:30Rules for responsible delivery
- 31:28Deployment vs release
- 39:00Multiversion unlocks value
- 42:33Q&A: Platforms and multiversion
related talks
33mContinuous Delivery - What does good really look like?
24mWhy, What, and How of Continuous Delivery
55mThe Rationale for Continuous Delivery
31mThe Continuous Delivery Paradox - Balancing Business Value with Speed
36mWhat do we know about continuous delivery – and what would we like to know
45mContinuous Delivery in a World of Constant Change
59mThe continuous culture
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases