Release is one of the final steps in the SAFe for DevOps Health Radar. At this point, the new functionality is already deployed to production and verified. Now it is time to make the new functionality available to a small group of users or to all users. In this video, I walk through what the Release step involves and why it is a crucial business decision.
In this article, I explain what Continuous Deployment is within the SAFe® DevOps Health Radar and why it is essential for delivering value quickly and safely. Please note that everything discussed here is under the license of Scaled Agile, and that the Scaled Agile Framework is a framework to be used as a toolbox. Take out of this toolbox what fits your needs and what solves your problems.
Continuous Deployment is the final, most aggressive step in the CI/CD progression. CI proves the code builds and the unit tests pass. Continuous Delivery proves the artifact works in a production-like environment. Continuous Deployment removes the last manual checkpoint: if every test along the way is green, the change goes straight to production. No “deploy” button, no Friday-afternoon release window, no human in the loop for the final step.
