Beyond Continuous Delivery: What Comes Next?
Tair Assimov
91

Does everybody necessary need Continuous Delivery?

By the way, the benefits you listed are not correct:

“Visibility: CD ensures that everyone is working off the latest version of the codebase all of the time”.

Wrong — you work off the latest version of the codebase if you rebase your branches regularly or don’t use branches. Nothing to do with CD.

“Improved quality: automated testing procedures and quality gates provide assurances”.

What it has to do with CD? You can have automated testing procedures and quality gates while not practicing CD (for this you need CI, not CD).

“Lower risk: the smaller the release, the less can go wrong”.

It does not matter if you release several changes together or one change at a time, if one change has a bug, things will go wrong. At least with weekly or bi-weekly releases it is clear that the problem is caused by the latest release and it is easier to figure out where to roll back the releaset.

“Lower costs: by automating your testing and deployment processes you reduce manual labor”

Again — what it has to do with CD? You can automate testing and deployment process, but still release once in two weeks, not every time you make a small change.

“Ownership & Engagement: everyone from developers, testers, and PMs are each held accountable for the software development lifecycle”

And what this has to do with CD?

If you want to come up with benefits, please come up with real benefits, not something that has nothing to do with Continuous Deployment.

Show your support

Clapping shows how much you appreciated Sceptical Meerkat’s story.