CoChat
Sign Up
Cited by 172Software Engineering Techniques and PracticesSoftware System Performance and ReliabilitySoftware Engineering Research

DevOps Capabilities, Practices, and Challenges: Insights from a Case Study

Open access
Senapathi, Mali, Buchan, Jim, Osman, Hady·2018·Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018
DOI 10.1145/3210459.3210465
Open this paper in CoChat — free accountOpen PDF

Abstract

DevOps is a set of principles and practices to improve collaboration between development and IT Operations. Against the backdrop of the growing adoption of DevOps in a variety of software development domains, this paper describes empirical research into factors influencing its implementation. It presents findings of an in-depth exploratory case study that explored DevOps implementation in a New Zealand product development organisation. The study involved interviewing six experienced software engineers who continuously monitored and reflected on the gradual implementation of DevOps principles and practices. For this case study the use of DevOps practices led to significant benefits, including increase in deployment frequency from about 30 releases a month to an average of 120 releases per month, as well as improved natural communication and collaboration between IT development and operations personnel. We found that the support of a number of technological enablers, such as implementing an automation pipeline and cross functional organisational structures, were critical to delivering the expected benefits of DevOps.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3210459.3210465

Cites

17 of 17 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

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?

  • Mali Senapathi et al. found that collaboration between the development and testing teams increases effectiveness.

    “They found that collaboration between the development and testing teams increases effectiveness.”

    From Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance (2023) · cites this paper as [95]

    The Conclusion (p. 11) reports increased collaboration between development and operations teams, not specifically between development and testing teams. In §6.4, Benefits Realised (p. 8), a tester says that knowledge of development and operations helps them work more efficiently. That supports a related benefit, but not the claimed finding about collaboration between the development and testing teams. (LLM, conf=0.85)

    Experimental — accuracy not yet measured

  • Adoption of DevOps closes knowledge gaps and enhances code quality.

    “Additionally, the adoption of DevOps closes knowledge gaps and enhances code quality.”

    From Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance (2023) · cites this paper as [95]

  • The perceived benefits of adopting DevOps found in the literature are Increased Release frequency, improved quality assurance (QA), and enhanced collaboration and communication.

    “The perceived benefits of adopting DevOps found in the literature are Increased Release frequency, improved quality assurance (QA), and enhanced collaboration and communication.[19] [20] [21] [22] [23]”

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

  • Lack of integrated testing tools to secure DevOps is a DevOps security challenge.

    “We reviewed those studies briefly and extracted all the challenging factors including lack of secure coding standards [2], [23], [80], [81], using unsuitable performance metrics for security evaluation [2], [69], [78], [79] and lack of integrated testing tools to secure DevOps [14], [52], [53], [71].”

    From Prioritization based taxonomy of DevOps security challenges using PROMETHEE (2020) · cites this paper as [52]

  • Lack of consistent security policies design and performance measures is a DevOps security challenge.

    “The enterprise generally lacks with consistence security polices design and performance measures [6], [19], [52], [72], [73] due to the rigid policy structure.”

    From Prioritization based taxonomy of DevOps security challenges using PROMETHEE (2020) · cites this paper as [52]

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 4

  1. [2][2] Debois, P. Devops: a software revolution in the making? Cutter IT Journal , 24, 8 (2011). -
  2. [10][10] Erich, F., Amrit, C. and Daneva, M. Report: Devops literature review. University of Twente, Tech. Rep (2014). -
  3. [19][19] Claps, G. G., Svensson, R. B. and Aurum, A. On the journey to continuous deployment: Technical and social challenges along the way. Information and Software technology , 57 (2015), 21-31. -
  4. [21][21] Humble, J. and Molesky, J. Why enterprises must adopt devops to enable continuous delivery. Cutter IT Journal , 24, 8 (2011), 6. -

Cited by

Sorted by citations

Related

Authors
Senapathi, M., Buchan, J., & Osman, H.
Affiliations
  • Auckland University of Technology (NZ)
  • Auckland, New Zealand
ORCID
Senapathi, Mali
Venue
Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018
Publisher
ACM
Published
2018-06-28
Pages
57-67
DOI
10.1145/3210459.3210465
OpenAlex
W2811155182
Cited by
172
References
16
Citations by year
2026: 8 · 2025: 22 · 2024: 30 · 2023: 31 · 2022: 36 · 2021: 25 · 2020: 14 · 2019: 5 · 2018: 1
FWCI
8.83
Type
conference paper
Language
en
Open access
Licence
www.acm.org/publications/policies/copyright_policy#Background (vor)
Locations
  • International Conference on Evaluation and Assessment in Software Engineering (EASE) (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
  • arXiv (Cornell University)
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
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
DevOps, development and operations collaboration, deployment frequency, software engineering practices, continuous delivery, organizational change

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