DevOps can represent a significant change to a company’s processes and operating models. It is not advisable to rush into transformation, and especially not to attempt to change everything at once. If agile practices and DevOps are not yet part of daily operations in the organization, it is recommended to start with small steps and initiate activities based on clear, identified development needs.

How can you succeed? We have compiled from our experience ten important points in this article that should be considered in development projects where the DevOps operating model is being implemented for the first time.

The DevOps operating model process in practice

1. Identify the current state of the organization

Strengths and challenges. Interview developers, testers, project managers, IT specialists, and end users.

2. Create a clear transformation plan: define the objectives

Define the process, timeline, organization, tools, and methods. If necessary, engage experienced methodology experts (Agile, Scrum, DevOps).

3. Practice the DevOps process and agile practices in a pilot project

It is recommended to start with a non-business critical project that still delivers value. For example, an internal development project is well suited for this purpose.

4. Bring together the right people

Broad-based expertise is important. The size of a DevOps team is not set in stone, but a team of more than ten people is already large. Select innovative and technically skilled individuals who can and want to work across traditional boundaries and who are willing to share their knowledge with others.

5. Define the tools to be used that support the DevOps process and agile practices

There are several options. Choose tools that best suit the product being developed. It is not always worth paying for expensive licenses if they are not already in place. Open source tools can also take you far.

6. Train and onboard each team member thoroughly in the DevOps process and tools

Clarify each person’s role.

7. In iteration planning, account for the time required for automation implementation

Automation implementation does not happen by itself; it requires significant work and maintenance.

8. Automation is one of the fundamental pillars of the DevOps operating model

It is not possible to automate everything instantly, so prioritize, start small, and add implementation in each iteration.

Set a goal to automate the entire development pipeline first in the CI environment. Later, add deployment and Ops automation to cover other QA and production environments.

9. Monitor and supervise 24/7

Make analytics and logs available to everyone through dashboard views. Alert and report anomalies immediately. Record observations in the backlog and address them in priority order.

10. Collect continuous feedback on the work

This applies to both the development process and the product being developed, such as the user interface of a new application. It is advisable to request regular feedback from end users for an extended period, not just during the implementation phase.