Amazon (hardback, kindle)

InformIT (pdf, epub, mobi)

中文 (in Chinese)
日本語 (in Japanese)
한국말 (in Korean)

You can also see a list of all my publications and talks, including slides, on the Publications page.

Upcoming talks

The 2014 State of DevOps Report Is Here!

DevOps, a movement of people who care about developing and operating reliable, secure, high performance systems at scale, has always — intentionally — lacked a definition or manifesto. However (and this is fascinating in its own right) that doesn’t mean that we can’t measure the impact of DevOps, or how good people are at doing it. The proof of this, and also of the startling impact of the DevOps movement, is now available in the form of the 2014 State of DevOps report (which you can download for free).

The report, a collaboration between Nicole Forsgren Velasquez, Gene Kim, Puppet Labs, and yours truly, surveyed over 9,200 people worldwide, covering a wide range of industries and types of organization. Our goal for the report was ambitious. We set out to measure IT performance, business performance, the impact of particular practices (such as continuous integration, test automation, and version control), and also culture, and then to discover to what extent they influenced each other. How, you might ask, do you measure these things like culture and organizational performance? Following Douglas Hubbard’s definition of measurement as “A quantitatively expressed reduction of uncertainty based on one or more observations,” it turns out that you can measure anything if you put your mind to it. The report describes both our methodology and the way we measured these apparent intangibles.

Indeed we not only measured these things: we have sound, statistically significant data that shows that culture and DevOps practices impact both IT performance and organizational performance. In direct contradiction to a popular narrative of the last ten years, IT matters — indeed, the results show it is a competitive advantage — and DevOps culture and practices are instrumental in achieving both high IT performance and organizational performance. Readers of this blog will be especially interested to learn that:

  • Trunk-based development, continuous integration, and automated testing measurably improve both IT performance and organizational performance.
  • Having a high-trust culture has a strong impact on both IT performance and organizational performance.
  • Using external change approval processes such as a change advisory board, as opposed to peer-based code review techniques, significantly impacts throughput while doing almost nothing to improve stability.
  • Job satisfaction is the biggest predictor of organizational performance, and using DevOps practices are good predictors of job satisfaction.

I’m very excited by the report. We improved on last year’s method for measuring IT performance. We showed how you can measure culture and organizational performance. Most important, the analysis of our enormous data set demonstrates definitively that the strategies championed by the DevOps movement work, and that they provide a competitive advantage to your business.

Many thanks to my collaborators, the fabulous team at PuppetLabs, and to all of you who took the survey.

You can download the 2014 State of Devops Report for free.

  • Bryce Schober

    Save yourself the register-to-download SPAM at go to

  • Jez Humble

    I deleted a comment from someone who posted the direct link. Yes, it’s trivially easy to get the direct link and bypass the form. But PuppetLabs put a ton of work into this report and so I’m not going have a direct link appear on my site.

  • Pingback: Issues with ITIL Change Management « Basil Vandegriend: Professional Software Development

  • Brett Baggott

    Jez, I don’t mean this as criticism, I’m a HUGE fan of you and of continuous delivery, however, I was expecting this report to contain backing data, and I’m not seeing that. Don’t get me wrong, there’s great info and recommendations and I really appreciate all the work that went into it. I guess I was expecting more of a “here’s what we recommend _and here’s why_”. The “here’s why” part is what I wanted to see more of. I’m at a new company and I’m in the position of trying to “sell” continuous delivery. I’ve already sold continuous deployment in some areas, be we have certain areas where, “we just can’t use all that continuous delivery stuff here”, which means those are the _exact_ areas that would benefit most from continuous delivery (in my experience). I’m having a hard time finding resources that show “here’s how you reshape from maintaining 15 release branches to sanity” and “here’s why you want to”. I was hoping to find some hard stats on the “here’s why you want to” part in this report. Having said that, thank you so much for compiling this information, and for sharing it with us.