Cited by 43Software Engineering Techniques and PracticesSoftware System Performance and ReliabilityInformation Technology Governance and Strategy

Capabilities and Practices in DevOps: A Multivocal Literature Review

Amaro, Ricardo, Pereira, Ruben, da Silva, Miguel Mira·2023·IEEE Transactions on Software Engineering

Abstract

Context.To meet the demands of customers and market, Information Technology (IT) organizations are seeking to implement DevOps. While many succeed in DevOps adoption, others lack the knowledge on how to incorporate DevOps culture, process, measurements, and techniques in their business. Thus, successful adoption is still inconsistent, highlighting the need to provide management with relevant information to support the development of DevOps Capabilities effectively. But what are these Capabilities? Unfortunately, there is still a lack of clarity about DevOps Capabilities and their relationships to DevOps Practices and Outcomes among researchers and practitioners.Objective.This research aims to gather community consensus on the relationship between Capabilities and Practices, so a better DevOps implementation can be mapped. Seeking to define DevOps Capabilities and Practices concepts and to identify, organize and summarize Capabilities as they relate to Practices.Method.A Multivocal Literature Review (MLR) is conducted, with 93 documents gathered and thoroughly examined from throughout the community, including books, scientific articles, white papers, and conferences, among others.Results.This survey contributes a list of 37 organized Capabilities, their mentions in literature, and their definitions. The concepts of Practices and Capabilities were mapped and categorized in an ordered taxonomy. It is concluded that industry research has much outweighed scientific research on this topic, with Capabilities evolving dynamically over time, reinforcingteam collaboration and communicationas the most crucial one. The study's Outcomes will assist researchers and practitioners understand how Capabilities and Practices are related at different levels and how to better implement them.

Integrity signals

Registry

Crossref · 10.1109/tse.2022.3166626

Cites

72 of 72 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • In current literature, the same practice, such as deployment automation, can be mentioned for both DevOps and DevSecOps which indicates overlapping between practices.

    “In current literature, the same practice, such as deployment automation, can be mentioned for both DevOps [16] and DevSecOps [51] which indicates overlapping between practices.”

    From DevSecOps practices and tools (2025) · cites this paper as [16]

  • In [16], Amaro et al., discuss and verify that practices and capabilities are interchangeable terms to describe the application of a method within the DevOps context.

    “In [16], Amaro et al., discuss and verify that practices and capabilities are interchangeable terms to describe the application of a method within the DevOps context.”

    From DevSecOps practices and tools (2025) · cites this paper as [16]

  • By leveraging the systematic mapping of DevOps practices found in [16] it is possible to compare which practices are mentioned in both approaches and how they are implemented in each approach.

    “Additionally, by leveraging the systematic mapping of DevOps practices found in [16] it is possible to compare which practices are mentioned in both approaches and how they are implemented in each approach.”

    From DevSecOps practices and tools (2025) · cites this paper as [16]

  • Although DevSecOps is still a recent topic, MLR has been previously applied to DevOps and DevSecOps.

    “Although DevSecOps is still a recent topic, MLR has been previously applied to DevOps [16] and DevSecOps [10].”

    From DevSecOps practices and tools (2025) · cites this paper as [16]

  • The perceived most common DevOps practices in literature are Continuous Integration, Continuous Delivery, Continuous Monitoring, and Continuous Testing.

    “The perceived most common DevOps practices in literature are Continuous Integration, Continuous Delivery, Continuous Monitoring, and Continuous Testing [14] [16] [17] [18] [19] [20].”

    From DevSecOps practices and tools (2025) · cites this paper as [16]

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Amaro, R., Pereira, R., & da Silva, M. M.
Affiliations
  • Iscte – Instituto Universitário de Lisboa (PT)
  • Instituto Universitário de Lisboa (ISCTE-IUL), Lisboa, Portugal
  • Instituto Superior Técnico, Universidade de Lisboa, Lisboa, Portugal
Venue
IEEE Transactions on Software Engineering
Published
2023-02-01
Volume
49
Issue
2
Pages
883-901
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W4226494241
Cited by
43
References
72
Citations by year
2026: 10 · 2025: 2 · 2024: 19 · 2023: 12
FWCI
8.17
Type
journal article
Language
en
Open access
closed
Locations
IEEE Transactions on Software Engineering (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Social Sciences › Business, Management and Accounting › Management Information Systems › Information Technology Governance and Strategy
Keywords
DevOps, DevOps practices, DevOps adoption, team collaboration, communication, IT organizations

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