Over a million developers have joined DZone.

Top Factors Holding Companies Back From Continuous Delivery

What factors are keeping companies from implementing continuous delivery, and why are they blockers?

· DevOps Zone

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

It seems like not a week goes by without the publication of a new study showing the benefits of building a continuous delivery process, this begs the obvious question: Why are some software development companies holding out? What are the main reasons why some organizations have not yet adopted continuous delivery?

Here is an informal list of frequent explanations I get from the holdouts:

Culture

In many of the bigger enterprises, the explanation is cultural rather than technical. With decades old companies that have massive models built around waterfall, including very expensive tools and processes, not to mention all the people whose job depends on continuing with waterfall, it can very difficult to make the changes necessary for continuous delivery. See Adobe for an example of massive 30+ year old company which has adapted continuous delivery.

Outside Opposition

Even if you convince the engineering teams that continuous delivery is the way to go, organizations can face opposition from other departments who will be impacted by the change in the app lifecycle. Sales teams, customer support, or the clients themselves may push to stick with the waterfall approach.

No Time

Continuous delivery is one of those investments where you can expect to put in a lot of time and effort upfront, to get major benefits down the road. Is the investment worth it? Of course it is, but when you’re an engineering team that’s on the clock to get the immediate projects done, it can be hard to spend the time necessary to improve your process.

Tech Fragmentation

In order to build a CD pipeline you must implement a system that plasters together numerous splintered services. You will have to assimilate your code repo, bug tracking, project management, deployment system, etc. It is uncommonly challenging to get all of them to work cohesively. And teams worry that once you do, you are closed into a specific technology or tool.

None of these are reasons to write off continuous delivery, but these are challenges to look out for when attempting to implement CD in certain organizations. Having said that, I firmly believe that every organization will inevitably move to this agile practice in the coming years.

Want to read more about continuous delivery? Download our popular free eBook – In Database Automation we trust.

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

Topics:
devops ,continuous delivery

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}