DevOps emerged in 2009 and over the last three years it has gained considerable momentum, albeit some of it contradictory, in the IT industry. Some loved it. Some lived it. Others changed their job title and moved on. Many hated it. Some have argued DevOps jumped the shark when the first analyst added it to their portfolio. Whatever side of the argument you fell on, the DevOps movement provoked a lot of discussion about the future of IT management. But has DevOps resulted in changes in the culture and processes of IT organisations? Has DevOps become another silo in your organisation? Or are you still asking “What the hell is DevOps?”
Sadly, I don’t think there are any definitive answers yet. We’ve seen a lot of practical examples, across a broad spectrum of industries and organisations, where DevOps has become de riguer. I’ve had conversations with startups (“We’ve always been DevOps—now there’s just a name for it”) to multi-nationals (“Now we talk to one another about workflow and deployment. It’s changed the way we do business”). Certainly the demand for “DevOps” roles has surged as evidenced by Indeed.com’s DevOps job trends graph below which shows sharp up and to the right growth.
Whilst DevOps penetration is nowhere near ubiquitous, the profile of DevOps has certainly increased. Together with buzz from the analysts, some of the larger IT tools players, companies like BMC, HP and IBM, have entered the space with DevOps-specific tools and frameworks. Some of these have arguably been hype-driven marketing movements rather than substantive new products, but we have seen a small trickle of product changes resulting from DevOps principles and workflows.
In addition, we’ve also seen DevOpsDays, DevOps meetups, and DevOps-related talks at conferences expand and grow. These talks have also changed in tenor. There are less “What’s this DevOps thing” or “This is the theory of DevOps and x” and more case studies, tools and practical examples. We’re now starting to hear the stories and the outcomes from people trying DevOps in their environments.
So in keeping with this theme, we’re going to feature blog posts from a number of DevOps practitioners that will focus on case studies and practical ways DevOps can change your organisation in a series we’re calling “DevOps December.”
- The first of these posts will be from Gene Kim, AKA the Granddaddy of DevOps, and author of The Visible Ops Handbook and upcoming novel The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.2>
- Next week we’ll get the Dev perspective with posts from Mitchell Hashimoto, writer of Vagrant and the founder of the brand-new HashiCorp, and our very own Puppet Enterprise developer Max Martin.
- Week 3 will be focused on how we do QA and release management with Puppet Labs QA Engineer, Dominic Maraglia and Jez Humble, author of Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation.
- Finally, in week 4, to close out the month, we’ll hear about DevOps culture from Ops pros and DevOps enthusiasts—Kelsey Hightower, Eric Shamow, and Mike Stahnke from Puppet Labs; Nick Galbreath and Patrick DeBois from the wider community.
In aid of understanding how DevOps has influenced your organisation, we’re also launching our annual DevOps survey. We want to hear all about the good, the bad, and the ugly aspects of your DevOps experience, so please take a moment to fill it out. In exchange for your thoughts, you’ll be entered in a drawing to win PuppetConf 2013 tickets, a copy of Gene Kim’s upcoming novel The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win, and Puppet Labs swag.
We hope these posts and sharing your thoughts in the survey inspire you to take a look at DevOps, provide some feedback on how others have implemented DevOps, or even get you thinking about bigger and better ideas for improving your organization.