Minimum Viable Continuous Delivery
summary
Describes how a team moves from quarterly releases to 10–12 deployments per day in about nine months by adopting trunk‑based development, daily continuous integration with ~85% confidence releasable, and a single automated delivery pipeline that serves as the emergency path. Calls out anti patterns like Dunning‑Kruger delivery and CD‑in‑name‑only where pipelines exist but testing, feature flags and small changes do not. Points to community work at minimumcd.org with contributors, signatures and a Dave Farley PR.
AI-written summary · about
chapters (13)
- 0:00Introduction to Minimum Viable Continuous Delivery
- 1:09Misconceptions on CD value
- 4:22Pitfalls in CD adoption
- 7:13Origin of Min CD project
- 9:44Defining Min CD behaviors
- 10:49Trunk based development
- 13:16Continuous integration
- 15:45Why trunk and CI matter
- 18:10The delivery pipeline
- 20:37Min CD as a journey
- 21:41How to start with Minimum Viable Continuous Delivery
- 23:25Key steps to Min CD
- 25:30Relentless improvement
related talks
33mContinuous Delivery - What does good really look like?
51mBetter software, faster: principles of Continuous Delivery and DevOps
55mThe Rationale for Continuous Delivery
01h 01mA team's transition to Continuous Delivery
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
30mModern Continuous Delivery
30mOur Continuous Delivery Journey
49mIncubating Continuous Delivery