DevOps Evolution: Many Paths to Success and Failure
September 26, 2018

In a DevOps evolution, there are many paths to success, but even more that lead to failure, according to the 2018 State of DevOps Report from Puppet.


This year’s report reveals the five stages of DevOps evolution and a pragmatic, prescriptive approach aimed at helping organizations get started with DevOps, replicate and scale existing pockets of success and make forward progress in their DevOps evolution. The 2018 State of DevOps Report maps organizations along an evolutionary scale based on how frequently they are using key practices. Organizations that are employing all the practices with a high frequency are highly evolved, or High. Those organizations employing few practices with low frequency are Low, and those doing some practices sometimes are Medium.

Among some of the key findings:

In a DevOps evolution, there are many paths to success, but even more that lead to failure — Every organization is different and for most, the DevOps journey isn’t linear. There are many starts and stops along the way, which can kill early momentum and lead to cynicism. Without a prescriptive path forward, organizations are struggling to scale their DevOps success beyond isolated teams.

On the DevOps evolutionary scale, 80 percent of respondent organizations are Medium. Almost 11 percent are Low and just under 10 percent are High. Though DevOps practices have become mainstream, it’s much harder to make the leap from Medium to High than it is from Low to Medium. Thus, organizations can gain a serious competitive advantage if they concentrate on further evolving their DevOps practices.

Executives have a rosier view of their DevOps progress than the teams they manage — For nearly every practice, C-suite respondents were more likely to report that DevOps practices were in frequent use. For example, 64 percent of C-suite respondents believe that security teams are involved in technology design and deployment versus 39 percent at the team level.

Additionally, 54 percent of C-suite respondents believe their organization automates security policy configurations versus 38 percent at the team level.

Highly-evolved organizations are 24 times more likely to always automate security policy configurations

Automating security policy configurations is a critical practice at the highest levels of DevOps evolution — Highly-evolved organizations are 24 times more likely to always automate security policy configurations compared to the least evolved organizations. This finding underscores how as organizations evolve, security policy becomes a part of operations, not just an afterthought when an audit looms. In other words, teams are automating security policy configurations initially for their own benefit, and as their understanding evolves, this automation evolves to work for the benefit of the entire organization.

"While DevOps practices have become far more well known across our industry, organizations continue to struggle to scale pockets of DevOps success more broadly across multiple teams and departments,” said Nigel Kersten, VP of Ecosystem Engineering at Puppet. "This year's report explores the foundational practices that need to be in place in order to scale DevOps success, and proves that success can only scale when teams are enabled to work across functional boundaries."

“This year’s report findings validate that foundational practices have a profound impact on an organization’s overall DevOps evolutionary journey and are key to scaling successes no matter how mature the DevOps transformation is within the organization,” said Andi Mann, Chief Technology Advocate, Splunk.

About the Report: Puppet has surveyed more than 30,000 technical professionals. This year’s survey garnered responses from more than 3,000 global technology professionals from organizations of all sizes and within multiple industries. It was written by Puppet and Splunk.

The Latest

November 14, 2018

What to automate? Which parts of the delivery process are good candidates? Which applications will benefit from automation? At first, those sound like silly questions. Automate all your repetitive processes. If you think that you'll do the same thing manually more than once, automate it. Why would you waste your creative potential and knowledge by doing things that are much better done by scripts? Yet, an average company does not adhere to that logic. Why is that? ...

November 13, 2018

I'd love to see more security automation deeply integrated into the development process. Everybody knows since the 1990s that security as an afterthought just doesn't work, yet we keep doing it. The reason, I think, is because it's very hard to automate security ...

November 09, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 5, the final installment, covers deployment and production ...

November 08, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 4 is all about security ...

November 07, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 3 covers the development environment and the infrastructure ...

November 06, 2018

DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 2 covers the coding process ...

November 05, 2018

Everyone talks about automating the software development lifecycle (SDLC) but the first question should be: What should you automate? With this question in mind, DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 1 starts with by-far the most popular recommendation: Testing ...

October 31, 2018

Halloween is a time for all things spooky, but not when it comes to your mobile app experience. A poor experience can not only scare off your customers but keep them away for good ...

October 30, 2018

As organizations have embraced open source, they have become polyglot — using multiple programming languages and technology stacks to accomplish software and hardware related tasks. Enterprises are caught between the benefits provided by a polyglot environment and the complexities and challenges these environments bring. Ultimately, if the situation remains unchecked, polyglot will kill your enterprise ...

October 29, 2018

Factor 5 of the Twelve-Factor App relates more to processes and advises strictly separating the build and run stages. The emphasis is on identifying and separating each stage of app development, and encouraging automation between each so as to accelerate the process ...

Share this