A proposal to systematize introducing DevOps into the software development process

TL;DR

This paper proposes a systematic approach to integrating DevOps into software development, aiming to streamline adoption, clarify team roles, and reduce conflicts, with practical validation in real-world organizations.

Contribution

It introduces a formalized method for implementing DevOps and defining team roles to accelerate adoption and minimize conflicts in software projects.

Findings

Improved implementation speed of DevOps processes.

Reduced team conflicts during adoption.

Validated approach in real organizational settings.

Abstract

The software development industry has been evolving with new development standards and service delivery models. Agile methodologies have reached their completion with DevOps, thereby increasing the quality of the software and creating greater speed in delivery. However, a gap regarding the formalization of its adoption and implementation doubts became relevant. My hypothesis is that, by systematizing the introduction of DevOps into the software development process and defining the function of the members of the DevOps team members, may well make it quicker to implement this process, thus reducing conflicts between the teams. As part of the investigation of this hypothesis, the result of the research will be applied in practical development environments i.e. in a Technology Agency of the State of the Brazilian Government and also at the Brazilian Company Neurotech in order to evaluate its effectiveness from metrics appropriate for DevOps environments.