Adopting DevOps in the real world: A theory, a model, and a case study
The DOI matches its Crossref record; 39 of the 39 references it cites were found in a registry or an index.
Abstract
Abstract DevOps is a set of practices and cultural values that aims to reduce the barriers between development and operations teams. Due to its increasing interest and imprecise definitions, existing research works have tried to characterize DevOps. Nevertheless, little is known about the practitioners’ understandingabout successful paths for DevOps adoption. Therefore, our goal is to detail real scenarios of DevOps adoption, presenting a theory, a model, and a case study. We used classic Grounded Theory to build a theory about 15 scenarios of successful DevOps adoption in companies from different domains and countries. We proposed a model (i.e., a workflow for DevOps adoption) and evaluated it through a case study at a Brazilian Government institution. We used a focus group to collect the company perceptions about DevOps adoption. This paper increments the existing view of DevOps by detailing real scenarios and explaining the role of each category during DevOps adoption. We provide evidence that collaboration is the core DevOps concern, contrasting with an existing wisdom that automation and tooling can be enough to achieve DevOps. Altogether, our results contribute to: generating an adequate understanding of DevOps, from the practitioners’ perspective; and assisting other institutions in the path towards DevOps adoption.
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
The Discovery of Grounded Theory: Strategies for Qualitative Research.
Wagner, H. R., Glaser, B. G., & Strauss, A. L. (1968) · Social Forces · doi:10.2307/2575405 · Cited by 46,361
The Discovery of Grounded Theory; Strategies for Qualitative Research
Glaser, B. G., Strauss, A. L., & Strutzel, E. (1968) · Nursing Research · doi:10.1097/00006199-196807000-00014 · Cited by 39,449
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 · cited 1×
“Tables 1 and 2 summarize our research goals using a GQM (Goals/Questions/Metrics) template [14].”
MethodMorgan, D. L. (1996) · Annual Review of Sociology · doi:10.1146/annurev.soc.22.1.129 · Cited by 2,353
‘Discovering’ chronic illness: Using grounded theory
Charmaz, K. (1990) · Social Science & Medicine · doi:10.1016/0277-9536(90)90256-r · Cited by 1,648 · cited 1×
“First, GT is a consolidated method in other areas of research — notably medical sociology [17], nursing [18], education [19], and management [20].”
MethodExperimentation in software engineering
(2013) · Choice Reviews Online · doi:10.5860/choice.50-5018 · Cited by 1,517
Guide to Advanced Empirical Software Engineering
(2008) · Springer eBooks · doi:10.1007/978-1-84800-044-5 · Cited by 1,003 · cited 2×
“[29], focus groups typically have between three and twelve participants, are designed to obtain personal perceptions of members of one or more groups”
BackgroundMethodThe Sage handbook of grounded theory
(2008) · Choice Reviews Online · doi:10.5860/choice.45-6250 · Cited by 561
Grounded 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
Proceedings of the 36th International Conference on Software Engineering
(2014) · doi:10.1145/2568225 · Cited by 467
Cited by
Kumar, R., & Goyal, R. (2020) · Computers & Security · doi:10.1016/j.cose.2020.101967 · Cited by 97
Capabilities 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
Navigating the DevOps landscape
Zhang, X., Zhao, P., & Jaskolka, J. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112331 · Cited by 21
A Unified Framework for Automating Software Security Analysis in DevSecOps
Aljohani, M. A., & Alqahtani, S. S. (2023) · 2023 International Conference on Smart Computing and Application (ICSCA) · doi:10.1109/icsca57840.2023.10087568 · Cited by 17
“It extends DevOps' goal of encouraging collaboration between developers and operators by engaging security specialists from the beginning of the software development lifecycle [4].”
BackgroundPinto, G., De Souza, C., Rocha, T., Steinmacher, I., Souza, A., & Monteiro, E. (2024) · Proceedings of the IEEE/ACM 3rd International Conference on AI Engineering - Software Engineering for AI · doi:10.1145/3644815.3644949 · Cited by 17
Self-citationMigration From DevOps to DevSecOps: A Complete Migration Framework, Challenges, and Evaluation
N., N. T., & Khandebharad, A. (2021) · International Journal of Cloud Applications and Computing · doi:10.4018/ijcac.2022010102 · Cited by 5
Metadata
- Authors
- Luz, W. P., Pinto, G., & Bonifácio, R.
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2019-11
- Volume
- 157
- Pages
- 110384
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2962826822
- Cited by
- 164
- References
- 39
- FWCI
- 22.49
- Type
- journal article
- Language
- en
- Open access
- closed
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.