Minimum Viable Continuous Delivery

April 8, 2022
A group of people with a lot broader experience than I have, come up with a pretty good definition of "Minimum Viable Continuous Delivery".

I wanted to expand a bit on what I wrote yesterday about what necessary components you need in place to achieve the benefits of continuous delivery.

Fortunately, a group of people with a lot broader experience than I have, have put their heads together and come up with a pretty good definition of “Minimum Viable Continuous Delivery” which is hosted at minimumcd.org. Let me share the highlights:

The minimum activities required for CD are:

There’s more to read on the site about Continuous Integration and Trunk-based development respectively, so I encourage you to read the entire page (it’s short).

I also interviewed Bryan Finster, one of the original authors of Minimum Viable CD, on the topic in Episode #21, in case you missed it.

Related Content

Adventures In DevOps 093: Deconstructing the Minimum Viable Continuous Deployment

The panel jumps in and discusses the Minimum Viable Continuous Deployment from the manifesto on the web and discuss where they agree and disagree with the requirements listed there and clarify some of the ideas in the document.

Different models of CI/CD

There's almost always more than one way to do something. What workflow does your team use for CI/CD?

Solo DevOps