A guidance to implement or reinforce a DevOps approach in organizations: A case study

In recent years, stakeholders expect the delivery of new features almost every day to give fast feedback about changes or issues in software projects. To achieve this, they have opted to try new practices such as those from DevOps to improve their processes. Organizations such as IBM, Facebook, Amazon, and so on are implementing a DevOps culture. However, for small organizations, which are a large majority in the software development market, it is complicated to adopt DevOps because there is no guide to follow. Organizations have experienced issues trying to implement a DevOps approach, mainly for reasons such as a lack of process, guidance, or uncoordinated activities among organizations. Moreover, some organizations have a wrong understanding of DevOps: as just a set of automation tools to achieve a continuous release. This paper presents a guide to implement or reinforce a DevOps approach. Besides, the results of a case study of implementing the guide in a small organization are included. These results have shown that the guide helped the team: to identify its gaps toward the implementation of a DevOps approach; to have a better understanding of DevOps; and to facilitate the DevOps implementation providing a set of tasks, roles, and metrics.