How do you implement DevOps?

DevOps seems to provide the right answer, by suggesting how to implement the right culture. Above all, it is worth noting that DevOps suggests an approach – it is not inventing an approach. DevOps reminds us that a culture is a group of people with a common set of shared attitudes, values, goals and practices. How do you create a culture around these Fab Four?

In rough terms it goes like this:

First, determine your core values and let Dev and Ops, as well as all your stakeholders, know about them.

Secondly, create clear and comprehensible goals which meet your business objectives and are consistent with your values. Start with the “why” in everything you do. Only then, and not before, move to the how.

Thirdly, establish practices that let the processes of Dev and Ops converge and move straight towards your goals.

Lastly, don’t forget to test all these against the attitudes of your Dev and Ops teams.

Implementing such a culture is one big challenge, but maintaining it is much more difficult. DevOps reminds us that we need to listen constantly and carefully to these attitudes in order to determine which values aren’t being embraced and which may need to be changed. Never forget for whom you are building your product! DevOps further reminds us not to panic when goals need to be re-examined and practices need to be adjusted in order to continuously move towards these goals. Taking actions like that is what motivates Dev and Ops to collaborate.

But what lets the processes of Dev and Ops converge? Indeed that is a big question. At its root, it’s all about efficiency and effectiveness.

It’s about focusing on the right things in the first place so you don’t simply become more efficient at tasks that don’t really matter. It’s about pairing modern Lean and Agile concepts with good old-fashioned management principles such as systems thinking, systems dynamics and the theory of constraints, among many others. DevOps is an ensemble of concepts that, while not all new, are catalyzed into a movement.

When?

Well, cultural change for the fun of cultural change makes no sense. DevOps gets into the game whenever cultural change is required to meet your business objectives. But, when is the right time to change? Always! Never stop doing it! It’s a continuous change. Why, you may ask? You always want to be the innovative player in the market and the leader in quality of customer service to continuously increase market share and your customer database. So do it, and then do it again.

Who?

And who should bring that glory home? It’s you. It’s only you! Who else could it be? There is nobody that mysteriously brings cultural change to your mind. And if there is such a magical DevOps team, keep in mind that their eyes are useless when your mind is blind.

In conclusion, I am well aware of that fact that this article is not the most technically accurate article on DevOps ever written. Frankly, that was not my intention. Rather, I aimed to create a shared understanding on the concept of DevOps. What do you think of my analysis? Do you agree? Leave a comment, and keep an eye out for following articles.

 

DevOps – Nothing Else Matters?! Part 1: What is DevOps?
DevOps – Nothing Else Matters?! Part 2: Why DevOps?

Tricentis acquired Flood IO load testing - learn more

LEARN MORE
X