Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review

Research output: Contribution to journalLiterature review

Standard

Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review. / Laukkanen, Eero; Itkonen, Juha; Lassenius, Casper.

In: Information and Software Technology, Vol. 82, 02.2017, p. 55-79.

Research output: Contribution to journalLiterature review

Harvard

APA

Vancouver

Author

Bibtex - Download

@article{b4830ca8f60942d394fa77a3dddc700c,
title = "Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review",
abstract = "AbstractContext: 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.",
keywords = "Continuous integration, Continuous delivery, Continuous deployment, Systematic literature review",
author = "Eero Laukkanen and Juha Itkonen and Casper Lassenius",
year = "2017",
month = "2",
doi = "10.1016/j.infsof.2016.10.001",
language = "English",
volume = "82",
pages = "55--79",
journal = "Information and Software Technology",
issn = "0950-5849",
publisher = "Elsevier",

}

RIS - Download

TY - JOUR

T1 - Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic Literature Review

AU - Laukkanen, Eero

AU - Itkonen, Juha

AU - Lassenius, Casper

PY - 2017/2

Y1 - 2017/2

N2 - AbstractContext: 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.

AB - AbstractContext: 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.

KW - Continuous integration

KW - Continuous delivery

KW - Continuous deployment

KW - Systematic literature review

U2 - 10.1016/j.infsof.2016.10.001

DO - 10.1016/j.infsof.2016.10.001

M3 - Literature review

VL - 82

SP - 55

EP - 79

JO - Information and Software Technology

JF - Information and Software Technology

SN - 0950-5849

ER -

ID: 8801354