Currently, many organizations are trying to implement the DevOps model in their IT department because it responds better to the challenges of the market. When we talk about more demanding customers, we mean end-users and business partners who provide services and products through online channels (webshops, mobile applications, social networks).
For the DevOps model to work well in practice, everyone in the organization must understand what this particular model is. For example, developers should understand the demands of the end-user when working on their part of the project.
Sales representatives must know how to explain (in everyday language) the benefits of the service they are selling. Finally, managers must know how to motivate their employees when introducing changes in working methods so that the employees understand the need for this and want these changes to be made.
The DevOps model is based on three main principles: communication, collaboration and integration:
- Communication – companies should introduce the so-called “two pizza rule” for project teams. According to this, each team working on a specific project should comprise not more than two people sitting at one table (so that they can get by with two pizzas). The team then conducts its work so that everyone understands what everyone else is doing and that this work fits into the overall project.
- Collaboration – it is necessary for colleagues to do something together. No one should work alone “in a vacuum”, but rather as part of a team or cooperation with others.
- Integration – the model requires that people inside the organization understand what the end-user needs, what business partners are doing and what challenges face customers. All these people need to be open to “outside influences” for learning how their work affects other areas of activity in the company.
The DevOps model enables companies to react more quickly when facing market challenges, affecting how such companies are structured. In addition, the DevOps model still has problems to be addressed before implementation on a global scale.
According to Forrester Research, in 2020, 70% of all companies will operate based on an advisory model. A similar estimate was made earlier by Gartner. Many companies are moving away from the production model because they want to better respond to market changes, which means that there is a continuous need for new solutions. Smaller teams often produce these solutions, which means that the advisory model is becoming more and more attractive.
Smaller project groups (which will work quickly on new challenges) can be set up within an organization or outsourced to external parties. So the main question becomes who should carry out this outsourcing – individual departments or companies that work based on an advisory model.
The answer largely depends on how much this process will create value-added. If, for example, only some routine tasks are carried out (for example, compiling specific reports), then it is possible to carry out the operations using existing personnel in the departments affected by outsourcing.
In contrast, if the company wants to create entirely new experiences for its customers (for example, launching a new service), this process is better carried out by an external specialist – which is why some companies prefer to organize their work based on advisory teams.
DevOps can significantly help in achieving success in IT projects. If these projects are carried out using the standard model, there is a 25% probability of success. This figure rises to 35% if project management uses an advisory model and to 51% if the team responsible for project work has at least some DevOps knowledge.
Moreover, it should be noted that many obstacles still stand in the way of the widespread implementation of DevOps. The first and most important is that many companies (and their employees) still believe that the main priority in IT is to ensure high levels of stability and continuity of operations, rather than focusing on customer satisfaction or even on their daily business.