The Continuous Delivery Paradox - Balancing Business Value with Speed
summary
Panelists argue that deployment velocity without business impact is misleading: 1,000 deployments a day can be vanity, and Log4J exposes non‑declarative, non‑self‑sufficient pipelines. Concrete fixes include feature flags, declarative CI/CD, and automating pipelines to the cited 85–90% level so developers stop waiting on ops, plus tying engineering metrics to revenue or NPS. They report small, frequent releases that produce measurable customer value beat raw speed for reducing waste and risk.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:56Continuous delivery mistakes
- 9:36Speed versus quality
- 13:51Beyond Dora metrics
- 19:52Deployment chunk size
- 26:33Business alignment
related talks
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
24mWhy, What, and How of Continuous Delivery
01h 00mDevOps – Value at Speed
51mBetter software, faster: principles of Continuous Delivery and DevOps
55mThe Rationale for Continuous Delivery
45mTurning continuous delivery into competitive business advantage
31mThe Continuous Culture
33mContinuous Delivery - What does good really look like?
