Cited by 52Software Engineering Techniques and PracticesSoftware System Performance and ReliabilityDigital Transformation in Industry

Management challenges for DevOps adoption within UK SMEs

Open access
Jones, Stephen, Noppen, Joost, Lettice, Fiona·2016·Proceedings of the 2nd International Workshop on Quality-Aware DevOps

Abstract

The DevOps phenomenon is gathering pace as more UK organisations seek to leverage the benefits it can potentially bring to software engineering functions. However substantial organisational change is inherent to adopting DevOps, especially where there are prior and established methods. As part of a wider piece of doctoral research investigating the management challenges of DevOps adoption, we present early findings of a six month qualitative diary study following the adoption of DevOps within a UK based SME with over 200 employees. We find that within our case study organisation, the DevOps approach is being adopted for the development of a new system used both internally and by customers. DevOps, conceptually, appears to be generally well regarded, but in reality is proving difficult to fully adopt. This difficulty is down to a combination of necessity in maintaining a legacy system, lack of senior management buy-in, managerial structure and resistance. Additionally, we are finding evidence of job crafting, especially with the software developers. Taken together, we put forward the argument that DevOps is an interdisciplinary topic which would greatly benefit from further management and potentially psychology oriented research attention.

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/2945408.2945410

Cites

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?

  • Less resistance to change and stable management structures may facilitate the adoption of DevOps.

    “In [109 ], The researcher noted that less resistance to change and stable management structures may facilitate the adoption of DevOps.”

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

    Section 4.2, “Management Structure and Resistance” (page unavailable), describes IT operations’ resistance and says the management structure enables disruption, supporting the point that less resistance may help DevOps adoption. It recommends a specific reporting arrangement—both teams reporting to the same line manager—but does not say that stable management structures facilitate adoption. (LLM, conf=0.87)

    Experimental — accuracy not yet measured

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

No references could be resolved yet.

Research works printed but not linked: 10

  1. L. Bass, R. Jeffery, H. Wada, I. Weber, and L. Zhu. Eliciting operations requirements for applications. In Proceedings of the 1st International Workshop on Release Engineering, pages 5-8. IEEE, 2013.
  2. L. Chen. Continuous delivery: Huge benefits, but challenges too. Software, IEEE, 32(2):50-54, 2015.
  3. N. Cook, D. Milojicic, and V. Talwar. Cloud management. Journal of Internet Services and Applications, 3(1):67-75, 2012.
  4. S. Hosono and Y. Shimomura. Application lifecycle kit for mass customization on paas platforms. In Services (SERVICES), 2012 IEEE Eighth World Congress on, pages 397-398. IEEE, 2012.
  5. S. W. Hussaini. Strengthening harmonization of development (dev) and operations (ops) silos in it environment through systems approach. In Intelligent Transportation Systems (ITSC), 2014 IEEE 17th International Conference on, pages 178-183. IEEE, 2014.
  6. Y. Liu, C. Li, and W. Liu. Integrated solution for timely delivery of customer change requests: A case study of using DevOps approach. International Journal of U-& E-Service, Science & Technology, 7(2):41-50, 2014.
  7. M. Loukides. What is DevOps? O'Reilly, 2012. Sebastopol, USA.
  8. A. Tseitlin. The antifragile organization. Communications of the ACM, 56(8):40-44, 2013.
  9. M. Walls. Building a DevOps Culture. O'Reilly, 2013. Sebastopol, USA.
  10. A. Wrzesniewski and J. E. Dutton. Crafting a job: Revisioning employees as active crafters of their work. Academy of Management Review, 26(2):179-201, 2001.

Cited by

Sorted by citations

Authors
Jones, S., Noppen, J., & Lettice, F.
Affiliations
University of East Anglia (GB)
Venue
Proceedings of the 2nd International Workshop on Quality-Aware DevOps
Publisher
ACM
Published
2016-07-21
Pages
7-11
OpenAlex
W2394743071
Cited by
52
References
0
Citations by year
2026: 1 · 2025: 1 · 2024: 8 · 2023: 9 · 2022: 10 · 2021: 7 · 2020: 9 · 2019: 3 · 2018: 2 · 2017: 1 · 2016: 1
FWCI
1.98
Type
conference paper
Language
en
Open access
Locations
  • International Workshop on Quality-Aware DevOps (QUDOS) (publishedVersion)
  • UEA Digital Repository (University of East Anglia) (submittedVersion)
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 › Engineering › Industrial and Manufacturing Engineering › Digital Transformation in Industry
Keywords
DevOps adoption, management problems, small and medium-sized enterprises, organizational change, legacy systems, management structure, resistance to change, job crafting, software developers, software engineering management

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