Many software engineering organizations around the world are adopting DevOps. One of the goals of DevOps is to foster better collaboration between development and operations personnel, in order to improve organizational efficiency. Since DevOps is lacking a common definition, there are several approaches to adopt it, and organizations largely need to determine how to apply DevOps for themselves. In this paper, we present results from a case study in which a software organization adopts DevOps. The focus of this research is to study the impact of mixing the responsibilities between development and operations engineers. We interviewed 14 employees in the organization during the study, and results indicate several benefits of the chosen approach, such as improved collaboration and trust, and smoother work flow. This comes at the cost of a number of complications, such as new sources for friction among the employees, risk for holistically sub-optimal service configurations, and more.
[1]
Manish Virmani,et al.
Understanding DevOps & bridging the gap from continuous integration to continuous delivery
,
2015,
Fifth International Conference on the Innovative Computing Technology (INTECH 2015).
[2]
Ivan Porres,et al.
DevOps: A Definition and Perceived Adoption Impediments
,
2015,
XP.
[3]
Robert Rosenberger,et al.
The problem with hands-free dashboard cellphones
,
2013,
CACM.
[4]
James Roche,et al.
Adopting DevOps practices in quality assurance
,
2013,
CACM.
[5]
Eric S. K. Yu,et al.
Modeling DevOps Deployment Choices Using Process Architecture Design Dimensions
,
2015,
PoEM.