DevOps in practice: A multiple case study of five companies
Open accessThe DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
Abstract Context: DevOps is considered important in the ability to frequently and reliably update a system in operational state. DevOps presumes cross-functional collaboration and automation between software development and operations. DevOps adoption and implementation in companies is non-trivial due to required changes in technical, organisational and cultural aspects. Objectives: This exploratory study presents detailed descriptions of how DevOps is implemented in practice. The context of our empirical investigation is web application and service development in small and medium sized companies. Method: A multiple-case study was conducted in five different development contexts with successful DevOps implementations since its benefits, such as quick releases and minimum deployment errors, were achieved. Data was mainly collected through interviews with 26 practitioners and observations made at the companies. Data was analysed by first coding each case individually using a set of predefined themes and thereafter perform a cross-case synthesis. Results: Our analysis yielded some of the following results: (i) software development team attaining ownership and responsibility to deploy software changes in production is crucial in DevOps. (ii) toolchain usage and support in deployment pipeline activities accelerates the delivery of software changes, bug fixes and handling of production incidents. (ii) the delivery speed to production is affected by context factors, such as manual approvals by the product owner (iii) steep learning curve for new skills is experienced by both software developers and operations staff, who also have to cope with working under pressure. Conclusion: Our findings contributes to the overall understanding of DevOps concept, practices and its perceived impacts, particularly in small and medium sized companies. We discuss two practical implications of the results.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Using thematic analysis in psychology
Braun, V., & Clarke, V. (2006) · Qualitative Research in Psychology · doi:10.1191/1478088706qp063oa · Cited by 194,414
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2012) · doi:10.1007/978-3-642-29044-2 · Cited by 4,460
Guidelines for conducting and reporting case study research in software engineering
Runeson, P., & Höst, M. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9102-8 · Cited by 3,862 · cited 3×
“The multiple-case study approach was selected because it gave the possibility to investigate DevOps at multiple levels of analysis and in a real context [51], [52].”
BackgroundMethodMicroservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016) · IEEE Software · doi:10.1109/ms.2016.64 · Cited by 735 · cited 5×
“Studies that report successful adoption of DevOps, wherein the benefits of DevOps are realised, have shown that its implementation involves changes in organisational structures and roles [15], system architecture [16], processes and tools amongst others [17].”
BackgroundMethodInfluentialGrounded theory in software engineering research: a critical review and guidelines
Stol, K.-J., Ralph, P., & Fitzgerald, B. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884833 · Cited by 470
What is DevOps?: A Systematic Mapping Study on Definitions and Practices
Jabbari, R., bin Ali, N., Petersen, K., & Tanveer, B. (2016) · Proceedings of the Scientific Workshop Proceedings of XP2016 · doi:10.1145/2962695.2962707 · Cited by 230
DevOps: A Definition and Perceived Adoption Impediments
Smeds, J., Nybom, K., & Porres, I. (2015) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-18612-2_14 · Cited by 158 · cited 3×
“High demand for skills and knowledge Steep learning curve for operations personnel and developers [34] [28] [15] [17]”
BackgroundInfluentialSoftware security in DevOps: synthesizing practitioners' perceptions and practices
Ur Rahman, A. A., & Williams, L. (2016) · Proceedings of the International Workshop on Continuous Software Evolution and Delivery · doi:10.1145/2896941.2896946 · Cited by 86 · cited 2×
“, continuous monitoring through log aggregation and monitoring tools has become an integral part of the deployment pipeline, and are made accessible to developers [23] [16] [37] [44] [28].”
BackgroundManagement challenges for DevOps adoption within UK SMEs
Jones, S., Noppen, J., & Lettice, F. (2016) · Proceedings of the 2nd International Workshop on Quality-Aware DevOps · doi:10.1145/2945408.2945410 · Cited by 52 · cited 3×
“Another challenge identified was that DevOps adoption necessitates that both software developers and system administrators learn new technologies, tools and methods, in addition to performing their ongoing activities [34] [17] [28] [15].”
Background
Cited by
Preliminary Findings about DevSecOps from Grey Literature
Mao, R., Zhang, H., Dai, Q., Huang, H., Rong, G., Shen, H., Chen, L., & Lu, K. (2020) · 2020 IEEE 20th International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs51102.2020.00064 · Cited by 49
“It is crucial that software teams have ownership and responsibility to deploy software changes in DevOps [6], which allows the software to be delivered quickly [7].”
MethodCapabilities and Practices in DevOps: A Multivocal Literature Review
Amaro, R., Pereira, R., & da Silva, M. M. (2023) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3166626 · Cited by 43
The evolution of software development orchestration: current state and an agenda for future research
Maruping, L. M., & Matook, S. (2020) · European Journal of Information Systems · doi:10.1080/0960085x.2020.1831834 · Cited by 41
Grande, R., Vizcaíno, A., & García, F. O. (2024) · Computer Standards & Interfaces · doi:10.1016/j.csi.2023.103767 · Cited by 30
Revisit security in the era of DevOps: An evidence-based inquiry into DevSecOps industry
Zhou, X., Mao, R., Zhang, H., Dai, Q., Huang, H., Shen, H., Li, J., & Rong, G. (2023) · IET Software · doi:10.1049/sfw2.12132 · Cited by 23
Metadata
- Authors
- Lwakatare, L. E., Kilamo, T., Karvonen, T., Sauvola, T., Heikkilä, V., Itkonen, J., Kuvaja, P., Mikkonen, T., Oivo, M., & Lassenius, C.
- Venue
- Information and Software Technology
- Publisher
- Elsevier BV
- Published
- 2019-10
- Volume
- 114
- Pages
- 217-230
- ISSN
- 0950-5849 (ISSN-L)
- OpenAlex
- W2954754777
- Cited by
- 195
- References
- 9
- FWCI
- 26.24
- Type
- journal article
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.