This is third post in the The Three Pillars of DevOps series
|Part 1 – The Three Pillars of DevOps|
Part 2 – Pillar #1 - Developers
Part 3 – Pillar #2 - Operations Engineers
Part 4 – Pillar #3 - Management
Part 5 – Bringing it all together
In this post we will dive in to the third pillar – Management.
Being part of the Pillar
DevOps is a cultural change
Most people do not like change. Personally, I do not have an easy time adapting to change, it makes me nervous, uncertain, unsure. Different people take to change in different ways. Adoption of a DevOps way of working is not a small thing.
Boundaries are no longer clear.
Who is in charge of what?
Why do we have to take care of this?
I have no idea of what this means.
With any big change you should understand what this will do to your organization. See where you will have problems. Where people will need help. Expect that things are going to change. Over time.
Support both of the other pillars on the journey
In continuation on the previous point. Help your developers with education. They are no longer responsible for a small part, but rather the big picture.
Help your Operations Engineers with the world of code, again training, courses, books, seminars, pair programming there are a more than a number of ways.
Bring in someone to help and coach your teams throughout the journey, going from waterfall to Agile is a huge change, even more so such a culture change. Help them in the beginning, through the ups and downs, and how they can continuously improve themselves and the way they work.
This is going to take time. Quite a lot of time. Give the teams the leeway to adapt and learn along the jurney. Let them learn from their mistakes, pave their own path. Your productivity will probably go down in the short term, which also mean that the bottom line might drop as well.
Be prepared for this. Remember, if you are in it for the short term, the quick win, then this is the wrong reason. And it will most probably fail. Almost definitely. Your are here for the long term, even if it means losing in the short term.
Not being part of the Pillar (or being Samson)
We should start doing DevOps! Now!
I went to this interesting seminar where they showed how they are delivering code 10-20 times a day. I want us to start do the same. Next week. Let’s just make some quick changes, merge some teams, get the Devs working together with the Ops, and we should be able to deliver even more often with better quality.
My employees can do double the work, in less time
So now that we are ‘doing DevOps’ I don’t need so many people on my teams because they are doing the work on both sides of the fence. They can get their work done and also support the applications they are writing from start to finish with less people, and because they are more efficient probably in less time.
There is only one way to get this done.
Agile, Extreme Programming, Kanban. Rally. We need one tool to monitor and rule it all. One process that everyone has to follow. Everyone has to fit into the box we create. That is the only way we can maintain control.
The groups have to adapt to the way I want it to work. My way or the highway.
Next up we will look at Part 5 of this series – Bringing it all together.