aalto1 untyped-item.component.html
Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review
Loading...
Access rights
openAccess
publishedVersion
URL
Journal Title
Journal ISSN
Volume Title
Literature review
This publication is imported from Aalto University research portal.
View publication in the Research portal (opens in new window)
View/Open full text file from the Research portal (opens in new window)
View publication in the Research portal (opens in new window)
View/Open full text file from the Research portal (opens in new window)
Authors
Laukkanen, Eero
Itkonen, Juha
Lassenius, Casper
Date
Department
Major/Subject
Mcode
Degree programme
Language
en
Pages
Series
Information and Software Technology, Volume 82, pp. 55-79
Abstract
Abstract Context: Continuous delivery is a software development discipline in which software is always kept releasable. The literature contains instructions on how to adopt continuous delivery, but the adoption has been challenging in practice. Objective: In this study, a systematic literature review is conducted to survey the faced problems when adopting continuous delivery. In addition, we identify causes for and solutions to the problems. Method: By searching five major bibliographic databases, we identified 293 articles related to continuous delivery. We selected 30 of them for further analysis based on them containing empirical evidence of adoption of continuous delivery, and focus on practice instead of only tooling. We analyzed the selected articles qualitatively and extracted problems, causes and solutions. The problems and solutions were thematically synthesized into seven themes: build design, system design, integration, testing, release, human and organizational and resource. Results: We identified a total of 40 problems, 28 causal relationships and 29 solutions related to adoption of continuous delivery. Testing and integration problems were reported most often, while the most critical reported problems were related to testing and system design. Causally, system design and testing were most connected to other themes. Solutions in the system design, resource and human and organizational themes had the most significant impact on the other themes. The system design and build design themes had the least reported solutions. Conclusions: When adopting continuous delivery, problems related to system design are common, critical and little studied. The found problems, causes and solutions can be used to solve problems when adopting continuous delivery in practice.
Description
Other note
Citation
Laukkanen, E, Itkonen, J & Lassenius, C 2017, 'Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review', Information and Software Technology, vol. 82, pp. 55-79. https://doi.org/10.1016/j.infsof.2016.10.001