What should I do to implement DevOps? A passionate road
What is DevOps?
Having seen what is DevOps in previous posts, the benefits it provides organisations that adopt this model, as well as the phases and tools that can be used, it is time to ask how you can implement these practices - and, if I may, culture - into your organisation.
The first aspect you need to know is that there is no magic recipe for philosophical change in any organisation. It would be wrong to think that the company should adapt to DevOps, as each company has a unique way of working, its own internal procedures, different clients, and a stack technology adapted to its needs. For all the above reasons, among other aspects, for successful implementation, the DevOps should adapt to each company.
You could think that applying DevOps is a process in which one day you get up, decide to apply it, and immediately start to use it. Taking such a large step would be extremely difficult, and the most likely outcome would be that you fall. In this case, the most important factor is to take small steps, little by little, and consolidate the current stage before moving to the next one. You must climb each rung of the ladder before you reach the desired level of implementation.
An extremely important part of the entire implementation process is perceiving the benefits of the change as soon as possible. If you choose to take a great leap, you will probably end up frustrated (not to mention the budgetary issues), turning the transformation process into a failure. On the other hand, if you manage to make small advances, you will start to see the advantages of applying these techniques quickly, both for the people responsible for the process as well as for any other person involved, which is going to spur you on to take more steps forward.
When you start to define the implementation, considering the previous information, an action plan must be conceived that focuses on the following aspects:
It is vital for people to become aware of their desire to implement cultural change in order for the wheels to start turning. When thinking about people you must consider everyone involved, right from the lowest levels of the organisation, through the intermediate positions, and of course, reaching the company’s top management.
Once everyone is convinced that they want to address this cultural change, you must focus on the process, starting, as we mentioned previously, with aspects that give the greatest benefit in a short period of time, for example, repetitive tasks that can be easily automated, giving the perception of very quick benefit and in alignment with expectations.
Finally, implementing the techniques and tools into your own products, such as practices of operation, monitoring, feedback, etc., which lead to overall greater satisfaction and quality.
To conclude, DevOps it is quite an exciting and fun process, though you must keep in mind that sometimes you have to take a step back so as not to fall into frustration. You must see it as a step forward that allows you to see development like engineering, and not as something very “crafted”. Not moving towards this model could mean getting left behind in the market, which is why it is well worth getting the journey started.