It's a trending news item that 150 miles NorthEast of San Francisco, Lake Oroville's water levels got so high so high that an emergency spillway on the dam had to be opened up. Almost 200,000 people are under evacuation orders as the water downstream may cause flooding. We hope and pray that the threat is mitigated.
Photo by Alan Light available under a Creative Commons Attribution-license
Which brings us to today's post about DevOps. If we replace water with code, you I am sure get the analogy. Rather than let the dam of code burst infrequently, DevOps provides an opportunity to do continuous builds/integration and continuous deployments but on a smaller more frequent interval.
What are the benefits? According to Puppet's “State of DevOps Report,” details that "high-performing DevOps organizations outperform their lower-performing peers. They deploy 200 times more frequently, with 2,555 times faster lead times, recover 24 times faster, and have three times lower change failure rates." Not bad.
Again the disclaimer with any of these metrics is that the gains are not universal and will depend on many variables. Besides the size of your organization, tools, and communication, the biggest factor is still cultural. Being humans we are creatures of habit and any time large systemic changes are brought in, we tend to resist. So go ahead open up the code spillway slowly and frequently in partnership with the downstream operations teams.