Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy)
Abstract
Rally Software transitioned from shipping code every eight-weeks, with time-boxed Scrum sprints, to a model of continuous delivery with Kanban. The team encountered complex challenges with their build systems, automated test suites, customer enablement, and internal communication. But there was light at the end of the tunnel - greater control and flexibility over feature releases, incremental delivery of value, lower risks, fewer defects, easier on-boarding of new developers, less off-hours work, and a considerable up tick in confidence. This experience report describes the journey to continuous delivery with the aim that others can learn from our mistakes and get their teams deploying more frequently. We will describe and contrast this transition from the business (product management) and engineering perspectives.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
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?
Immature automated deployment tools is a DevOps security challenge.
“The other frequently occurred challenge in an organization to secure DevOps activities is immature automated deployment tools [61], [81], [82], due to lack of testing knowledge.”
From Prioritization based taxonomy of DevOps security challenges using PROMETHEE (2020) · cites this paper as [61]
Cites
Psychological Safety and Learning Behavior in Work Teams
Edmondson, A. (1999) · Administrative Science Quarterly · doi:10.2307/2666999 · Cited by 12,026 · see citing works
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
Humble, J., & Farley, D. R. (2010) · Cited by 911 · see citing works
The Principles of Product Development Flow: Second Generation Lean Product Development
Reinertsen, D. G. (2009) · Cited by 228 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Continuous software engineering and beyond: trends and challenges
Fitzgerald, B., & Stol, K.-J. (2014) · Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering · doi:10.1145/2593812.2593813 · Cited by 212 · see citing works
DevOps Adoption Benefits and Challenges in Practice: A Case Study
Riungu-Kalliosaari, L., Mäkinen, S., Lwakatare, L. E., Tiihonen, J., & Männistö, T. (2016) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-49094-6_44 · Cited by 154 · see citing works
Prioritization based taxonomy of DevOps security challenges using PROMETHEE
Rafi, S., Yu, W., Akbar, M. A., Alsanad, A., & Gumaei, A. (2020) · IEEE Access · doi:10.1109/access.2020.2998819 · Cited by 50 · see citing works
Bhanushali, A. (2023) · International Journal of Science and Research (IJSR) · doi:10.21275/sr231021114758 · Cited by 11 · see citing works
Model to reduce DevOps pipeline execution time using SAST
Saurabh, S. K., & Kumar, D. (2024) · International Journal of System Assurance Engineering and Management · doi:10.1007/s13198-024-02262-6 · Cited by 10 · see citing works
- Authors
- Neely, S., & Stolt, S.
- Venue
- 2013 Agile Conference
- Publisher
- IEEE
- Published
- 2013-08
- Pages
- 121-128
- OpenAlex
- W2067937778
- Cited by
- 124
- References
- 3
- Citations by year
- 2026: 1 · 2025: 6 · 2024: 6 · 2023: 5 · 2022: 10 · 2021: 15 · 2020: 13 · 2019: 7 · 2018: 13 · 2017: 18 · 2016: 13 · 2015: 15 · 2014: 2
- FWCI
- 8.03
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Agile Conference (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
- Keywords
- continuous delivery, Kanban, Scrum, deployment frequency, build systems, test automation, internal communication, defect reduction, developer onboarding, product 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
