CD advocates claim that it lets organizations rapidly, efficiently, and reliably bring service improvements to market and eventually stay a step ahead of the competition.1 This sounds great. However, implementing CD can be challenging— especially in the context of a large enterprise’s existing developmentand-release environment.
So, how does workflow actually work in continuous delivery environments? How do companies make it happen? What kinds of pains have they experienced that have pushed them to adopt workflow techniques? And what kinds of benefits are they getting?
Once an organization has acquired the essential skill set to provision and manage infrastructure, set up delivery pipelines and analyze logs and metrics, it will then gradually face more complex decisions. Decisions that depend much more on the type of systems architecture and organizational structure than on individual tool choices.
So whether you’re a working at the sharp end in development and operations or in the management treadmill how do find and put to work all the DevOps business goodness and not end with another trendy IT white elephant? I have some surprising, but simple advice that starts and ends where it’s most effective – with you.
DevOps probably isn't killing developers. But it is changing how people think about development - from running projects to a focus on building and running services. And more importantly, DevOps is killing maintenance, or sustaining engineering, or whatever managers want to call it. And that's something that we should all celebrate.