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, Amaz...

Full description

Saved in:
Bibliographic Details
Published in:Journal of software : evolution and process 2024-03, Vol.36 (3), p.n/a
Main Authors: Muñoz, Mirna, Rodríguez, Mario Negrete
Format: Article
Language:English
Subjects:
Case studies
case study
DevOps
guidance
ISO/IEC 29110
Organizations
process
Software development
state of the art
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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. In recent years, stakeholders expect the delivery of new features almost every day. To achieve it, they opted to try practices such as those from DevOps. However, small organizations, which are a majority in the software development market, have experienced issues trying to implement a DevOps approach without a guide. Our research provides a guide to implement DevOps or to reinforce their DevOps approach and results of a case study of a VSE that use the guide to implement DevOps.
ISSN:2047-7473
2047-7481
DOI:10.1002/smr.2342