Avoid a big up-front investment in automation by building it piece by piece, as needed.

What's preventing you from releasing on demand, in 20 minutes or less?

Bryan Finster is a co-creator of Minimum Viable Continuous Delivery, and in this episode we talk about how this concept was born, what problems it aims to address, and how you can use it on your team to improve your continuous delivery.

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.

CD takes the concept of a CI pipeline to its logical conclusion. But that doesn't mean you have to implement a complete CI pipeline first.

By working in smaller iterations, we don't just re-organize our work, we actually reduce the amount of work we do.

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

CD leaves room for manual approvals, but once approved, all changes should be applied automatically.

Jonathan Hall joins the Adventure this week to discuss the advice he gives to clients to start continuous deployment before they have automated tests around their code.

We automatically created a test environment for every pull request, and it had a revolutionary impact on the development process.

As usual, the biggest obstacle to Continuous Deployment was the fear of losing control.