DevOps still lacks a commonly accepted definition, as discussed recently in the blog post The Problem with Defining DevOps. Kind of obvious in retrospect, but this really complicates meaningful usage of the word, particularly when used outside of the DevOps community.
You know what, I am starting to despair of the IT industry, just a little bit.
I’ve been working in IT for just over 20 years - I was very lucky to ride the greatest wave we’ve seen, the dawn of the Internet (I worked for the largest corporate ISP in the world, UUNET, from early 1996 to 2001), and I’ve worked in the slowest, most immobile companies you can imagine (Investment Banks). And in the last 5–10 years I’ve seen less and less common sense be applied. And now we have this word that nobody can truly define. And it’s creating even more silliness. People are spending energy, lots of energy, debating this phrase and its definition (the irony of this post is not lost on me).
There's an old idea in Hollywood— if you can't pitch an idea in one sentence, it's too complicated. The term "DevOps" is about 5 years old, and the community still has no consensus on what that word really means, even though it's full of thought leaders who'll claim to be able to tell you.
DevOps is a relatively new concept in comparison to Agile development, so it should come as little surprise that IT enterprises have a myriad of experiences and instances of Agile approaches. And there is no need to throw everything out and start over - both Agile and DevOps are complimentary. But what if after careful deliberation inside of your enterprise you've decided to evolve from Agile to DevOps? How can you ensure that you keep all the good things that Agile provided yet apply some of the learnings from the early adopters of DevOps principles? Building a DevOps state of mind requires more than giving developers root, installing a configuration management tool, using a source code repository, and proclaiming ‘yes, we’re a DevOps shop.” At the end of the day all aspects of the people, process, technology continuums get impacted by DevOps. Here are 5 key steps to work through when implementing DevOps in an IT enterprise where Agile rules:
The rise of DevOps teams is upon us. The most recent State of DevOps survey found that 16% of respondents were part of a DevOps department with 55% of respondents self-identifying as DevOps engineers or systems engineers. Interesting. And if you simply Google ‘DevOps jobs’ you get over 4.5 million hits. So like it or not, this DevOps thing is going mainstream.
In the DevOps webisphere, there are plenty of blogs, articles, commentary, pundits and ideas floating around to keep you busy until your head explodes. We here at ScriptRock tend to have a somewhat cynical perspective on things because we've spent years trying & failing to 'do DevOps' (by the way.... DevOps is NOT a verb for the good of the order) which is what lead us to creating the company to begin with. Our culture promotes having fun and we try to keep a sense of humor about stuff. We all know that a picture is worth a thousand words, so here are our top 5 favorite internet memes related to DevOps.
Most leading IT enterprises have some form of Agile development in place in their organization. Thereby, many organizations, websites, blogs, and companies exist to provide information about and support for Agile development. Here is a list of 10 key online resources to support your Agile journey.
Just like just a few years ago when we were in the early days of the cloud, we’re in the early days of DevOps. The DevOps Summit had by my estimation 50-100 people talking DevOps this year and I would imagine this will exponentially increase over the next few years as this topic continues to turn IT on it’s head. It is the shiny new toy for Enterprise IT! I was thankful to have the opportunity to be there and hear some of the best and brightest. Here are a few of the things I heard.
Puppet Labs just released the 2014 State of DevOps Report. The research team interviewed companies from multiple industries and various sizes, from startups to global firms with over 10,000 employees and had over 9,200 respondents in all. The report shows us that not only is DevOps working within the enterprise, but it is also driving higher employee satisfaction.
Here at ScriptRock, we like to look at DevOps through the lenses of Collaboration and Automation. Almost all vendors in the DevOps space focus on the latter. We've written about how this creates Zero Sum DevOps and how these 'pockets of automation' can lead to silos of expertise around specific tools which is counter to DevOps principles to begin with. Furthermore, we've have talked about how there are 3 Reasons IT automation tools suck at collaboration.