Of course you’re not an idiot. However, after getting asked the same question over and over, I got tired of members of my organization thinking I was hiding a magic formula and decided to write a super easy guide to spot DevOps transformation opportunities. This guide helps teams, agile coaches, managers identify opportunities to implement DevOps practices when some common problem statements occurs.
So DevOps has hit your organization, you’re hearing the term passed around every other week. What does this mean for you organization, team, and job? Isn’t DevOps just automation? Could your role, or entire team be eliminated, with some tools doing your job? You may be surprised to find that, while DevOps does include automation, DevOps doesn’t work without teams. DevOps is a potent mix of tools, processes, I.T. practices, and most importantly, teams. Without teams, DevOps doesn’t really exist. The right implementation of DevOps improves the quality of the major (and minor) IT roles. This means it’s easy to know when a DevOps implementation isn’t working. Will you have to work differently in your role to get the most out of DevOps imlpementation? Probably. Will you definitely lose your job because of a DevOps adoption at your organization? Probably not. This article breaks down how DevOps affects the general roles in most IT organizations; from developers to operations engineers to QA, and management.
We’ve kicked off DevOps transformation in the last few months and recently we started getting some feedback coming in. For example, “We’re not seeing anything.” The initial reaction was to intensify the publicity and branding, but thankfully cooler heads prevailed, and we stuck to our game plan. DevOps and Agile go hand-in-hand, like lightning and thunder. You see one, and hear (and even feel) the other. And that’s not saying the Agile transformation is all flash. It just means that not seeing “anything” doesn’t mean something isn’t happening.