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

Challenges in Adopting Continuous Delivery and DevOps in a Globally Distributed Product Team: A Case Study of a Healthcare Organization

Gupta, Rajeev Kumar, Venkatachalapathy, Mekanathan, Jeberla, Ferose Khan·2019·2019 ACM/IEEE 14th International Conference on Global Software Engineering (ICGSE)
DOI 10.1109/icgse.2019.00020
Open this paper in CoChat — free account

Abstract

This paper presents our experiences in a project of a software engineering team spread across three countries that successfully established continuous delivery, DevOps and short release cycles with agile scrum. We had the challenge to find a way from established regulatory heavy-weight processes, long release strategies, legacy tools and technologies and people mindset towards adopting continuous delivery and DevOps. We are describing our experiences in the journey towards timeboxed release strategies compared to legacy fixed scope-based releases; value stream-based execution compared to traditional milestone-based execution; operation, test, and infrastructure as a code compared to executing these activities manually. This paper also describes experiences in transforming traditional scrum team into a DevOps team, technological landscape into lightweight tools. The authors bring their experiences as a Project Manager, Quality Manager, and an Architect, who has been an integral part of this journey. These practices have helped in stabilizing processes and methods to an extent where we have released several products versions within a year. The other business units are adopting our practices for continuous delivery and DevOps. This paper also summaries our lessons learned, and recommendations.

Integrity signals

Registry

Crossref · 10.1109/icgse.2019.00020

Cites

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?

  • Paper S2-ACM-04 (Gupta et al., 2019) presents an empirical study on a global software project of the development team distributed geographically across India, the USA and Germany, that successfully adopted DevOps.

    “Paper S2-ACM-04 (Gupta et al., 2019) presents an empirical study on a global software project of the development team distributed geographically across India, the USA and Germany, that successfully adopted DevOps.”

    From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Gupta et al., 2019

  • Authors identified challenges and practices when adopting global DevOps.

    “Authors identified challenges and practices when adopting global DevOps.”

    From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Gupta et al., 2019

Cites

Still being checked.

Cited by

Sorted by citations

Related

Authors
Gupta, R. K., Venkatachalapathy, M., & Jeberla, F. K.
Venue
2019 ACM/IEEE 14th International Conference on Global Software Engineering (ICGSE)
Publisher
IEEE
Published
2019-05
Pages
30-34
DOI
10.1109/icgse.2019.00020
OpenAlex
W2966744039
Cited by
50
References
0
Citations by year
2026: 2 · 2025: 2 · 2024: 9 · 2023: 12 · 2022: 15 · 2021: 4 · 2020: 6
FWCI
4.98
Type
conference paper
Language
en
Open access
closed
Licence
Locations
IEEE International Conference on Global Software Engineering (ICGSE) (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
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
continuous delivery, DevOps, globally distributed teams, Agile Scrum, value stream, infrastructure as code, test automation, legacy software, regulatory process, medical software, organizational change, lessons learned

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