This post originally appeared on New Relic.
Author and DevOps guru Gene Kim spent more than five years of intense research on The DevOps Handbook. Along with co-authors Jez Humble, Patrick DeBois, and John Willis, Gene offers real-world examples and advice on how to maximize the power of DevOps.
Currently the organizer of the DevOps Enterprise Summit, Gene is probably best known for founding Tripwire back in 1997 and for co-writing the seminal book The Phoenix Project: A Novel About IT. Gene’s latest journey deep into the DevOps movement cemented his long-held conviction that companies looking to go from good to great should get in on the DevOps action—and fast.
At our latest FutureTalk in Portland, Oregon, Gene shared some of his most surprising findings, offering fascinating proof (via real-world case studies) of the power of DevOps to transform not just engineering practices but the enterprise as a whole. Ultimately, he said, the goal of DevOps should be to make all 16 million of the world’s engineers as efficient and effective as those working at companies like Facebook or Google.
Here are just a few of his surprising findings:
Surprise #1: The Business Value of DevOps Is Even Higher Than We Thought [Time Code 1:58]
Companies that practice DevOps outperform those that don’t. This, Gene said, was not necessarily shocking, but what did blow him away was the sheer magnitude of that outperformance. Compared with their low-performing peers, the top DevOps-embracing organizations are
- More agile (they have 200 times more frequent deployments and 2,555 times shorter lead times).
- More reliable (they record 3 times lower change-failure rates and 24 times faster mean time to recover).
- More secure (they spend half the time on security issues and 29% more time on new work).
Even more amazingly, these organizations are twice as likely to exceed profitability, market share, and productivity goals, and they enjoy 50% higher market capitalization growth over three years. As if that wasn’t enough, these organizations are also winning big in the labor marketplace, enjoying employee Net Promoter Scores that are 2.2x higher than companies that don’t follow a DevOps model.
Drilling down into this data, Gene found a particularly telling correlation. When low performers add more developers to their teams, the number of deployments per day goes down. But when high performers (DevOps shops) do the same, their rate of deployments increases.
“With the right architecture, the right cultural norms, and the right technical practices, we can actually scale developer productivity linearly as we increase the number of developers,” said Gene.
Surprise #2: DevOps Is as Good for Ops as It Is for Dev [9:35]
Quoting Nathan Shimek, an engineering manager at New Context who had to work even on the day his son was born, Gene said that ops has long needed to be made “more humane.” After all, even night owls hate getting paged at 2 a.m.
The truth is, hastily fixing defects in someone else’s code is neither efficient nor particularly satisfying. Citing the famous case study about the rollout of Facebook Chat as an example, Gene showed how devs testing in production isn’t always as crazy as he once thought it was. For one thing, developers are often faster at fixing their own glitches. And many devs find great satisfaction in taking responsibility for their code all the way through to deployment and even fixing problems when they occur in production.
In other words, DevOps “brings the joy back to development work,” lessens sleep deprivation for ops, and generally improves relations between two breeds of engineer who have far more in common than the silos of old would suggest.
To hear the rest of Gene’s surprises, including #6: DevOps is for unicorns AND horses, watch his full FutureTalk in the video below: