Are you ready for continuous delivery? This article explains how an established, iterative development practice puts you on the right path.
If you aren’t practicing iterative development, you aren’t ready for continuous delivery.
If you aren’t doing automated testing, you aren’t ready for continuous delivery.
If you don’t have a quick way to see what happens to code when it’s deployed on your infrastructure, you aren’t ready for continuous delivery.
If you don’t have a staging environment for review before production release, you aren’t ready for continuous delivery.
If the business you work for hasn’t made a commitment to continuous delivery, you cannot reap the full benefit of ongoing, rapid software releases.
In this two-part series, Caum and other continuous delivery experts outline those problems — which define the prerequisites for charting a course to continuous delivery. This article, the first in the series, discusses what continuous delivery is, and explains how an established, iterative development practice sets the foundation for this new way of releasing software.
The second article in the series examines why automated testing, adopting infrastructure-as-code practices and establishing a staging environment are essential aspects of this new approach to delivering software.
Neither tip in this two-part series focuses primarily on the business benefits of continuous delivery. But it bears repeating that software organizations cannot succeed at continuous delivery unless they make a sustained commitment to this process. “Fundamentally, continuous delivery is a business decision, and if management doesn’t get it, it’s a tough sell.” said Mary Poppendieck, co-author with Tom Poppendieck of The Lean Mindset, among other books.