A Reflection on Puppet and DORA’s State of DevOps Report 2017

Written by Stefan Thorpe
2017 State of #DevOpsReport

This week saw Puppet’s release of its annual State of DevOps report; the oft-quoted research that every DevOps practitioner across the globe will be intimate with. In collaboration with DORA—DevOps Research and Assessment—Puppet has been measuring the evolutionary impact of DevOps on IT performance for the last six years through a survey of a record 27,000 IT professionals. Each year, the research analyzes the statistical—and dramatic—development of high- and low- performing IT teams. Teams who are all striving to deliver “software faster, more reliable, and with fewer errors” in line with DevOps best practices.

Puppet’s State of DevOps Report Webinar

On June 8th, two of the report’s authors—director of product marketing Alanna Brown and chief technical strategist Nigel Kersten—discussed the latest findings on a Puppet moderated webinar. Top of their discovery is the rise in DevOps adoption gaining traction in IT. In 2014, 16% of the survey respondents worked on DevOps teams; the 2017 research indicates 27% now work on such a team.

Interestingly, this year’s report places focus on how DevOps can work for all organizations, from for-profit to not-for-profit. It concentrates on the connection the DevOps language creates between IT and the rest of the business; whatever that business may be. Nigel Kersten explains, “The goal is not just to ‘do’ DevOps—not just ‘do’ digital transformation. The goal has to ultimately be about shipping value to the business. And being connected to the rest of the business is one of the most interesting developments of the report.”

Puppet used a snowballing method to reach out to 3,200 respondents across a diverse range of organizations and industries. By using statistical cluster analysis, Puppet segmented the survey respondents into high, medium, and low-performance groups. This is based on the teams functionality across four key measures: deployment frequency, lead time for changes, Mean time to recover (MTTR), and change failure rate.

What Does High-Performing Mean?

To become “high-performing,” the DevOps Report reinforces that organizations should be all about automating processes. Allowing the business to focus on delivering customer value and higher order initiatives. This research aligns with Caylent’s vision of the future and our product. As Alanna Brown deftly put it, “Automation is a critical differentiator for organizations. It’s the only way you’re going to accelerate your business and solve tomorrow’s problems.”

Our simple infrastructure deployments and fully automated continuous deployment (CD) systems empower teams. By enabling them to automate processes and compete with the high performers who already automate 30% more of their deployment. CD contributes to “both lower deployment pain and higher IT performance.” Caylent’s DevOps Container Management system aims to meet this market niche. We handle all the orchestration and automation, this way you can simply focus on building and testing code. In true DevOps style.

Thank you to the 2017 State of DevOps Report authors Dr. Nicole Forsgren, Gene Kim, Jez Humble, Alanna Brown, and Nigel Kersten.

 

Keen to learn more about DevOps? Check out my summary series on The DevOps Handbook. I take you through the book in bite-size chunks to save you time. Read from the start here: The DevOps Handbook: Introduction Summary to Everything You Need to Know.

Related Posts

The DevOps container management platform

  • Amazon AWS
  • Microsoft Azure
  • Google Cloud
  • Digital Ocean

Unlimited users. Unlimited applications. Unlimited stacks. Easily manage Docker containers across any cloud.

Get Started—Free!
Top
%d bloggers like this: