Improving the Delivery Cycle: A Multiple-Case Study of the Toolchains in Finnish Software Intensive Enterprises

Tutkimustuotos: Lehtiartikkeli

Standard

Improving the Delivery Cycle: A Multiple-Case Study of the Toolchains in Finnish Software Intensive Enterprises. / Mäkinen, Simo; Leppänen, Marko; Kilamo, Terhi; Mattila, Anna-Liisa; Laukkanen, Eero; Pagels, Max; Männistö, Tomi.

julkaisussa: Information and Software Technology, Vuosikerta 80, 12.2016, s. 175-194.

Tutkimustuotos: Lehtiartikkeli

Harvard

APA

Vancouver

Author

Mäkinen, Simo ; Leppänen, Marko ; Kilamo, Terhi ; Mattila, Anna-Liisa ; Laukkanen, Eero ; Pagels, Max ; Männistö, Tomi. / Improving the Delivery Cycle: A Multiple-Case Study of the Toolchains in Finnish Software Intensive Enterprises. Julkaisussa: Information and Software Technology. 2016 ; Vuosikerta 80. Sivut 175-194.

Bibtex - Lataa

@article{9d84dddec19043669e6aacef0654a1ad,
title = "Improving the Delivery Cycle: A Multiple-Case Study of the Toolchains in Finnish Software Intensive Enterprises",
abstract = "Context: Software companies seek to gain benefit from agile development approaches in order to meet evolving market needs without losing their innovative edge. Agile practices emphasize frequent releases with the help of an automated toolchain from code to delivery.Objective: We investigate, which tools are used in software delivery, what are the reasons omitting certain parts of the toolchain and what implications toolchains have on how rapidly software gets delivered to customers.Method: We present a multiple-case study of the toolchains currently in use in Finnish software-intensive organizations interested in improving their delivery frequency. We conducted qualitative semi-structured interviews in 18 case organizations from various software domains. The interviewees were key representatives of their organization, considering delivery activities.Results: Commodity tools, such as version control and continuous integration, were used in almost every organization. Modestly used tools, such as UI testing and performance testing, were more distinctly missing from some organizations. Uncommon tools, such as artifact repository and acceptance testing, were used only in a minority of the organizations. Tool usage is affected by the state of current workflows, manual work and relevancy of tools. Organizations whose toolchains were more automated and contained fewer manual steps were able to deploy software more rapidly.Conclusions: There is variety in the need for tool support in different development steps as there are domain-specific differences in the goals of the case organizations. Still, a well-founded toolchain supports speedy delivery of new software.",
keywords = "Continuous deployment, Continuous delivery, Software development tools, Deployment pipeline, Agile software development",
author = "Simo M{\"a}kinen and Marko Lepp{\"a}nen and Terhi Kilamo and Anna-Liisa Mattila and Eero Laukkanen and Max Pagels and Tomi M{\"a}nnist{\"o}",
year = "2016",
month = "12",
doi = "10.1016/j.infsof.2016.09.001",
language = "English",
volume = "80",
pages = "175--194",
journal = "Information and Software Technology",
issn = "0950-5849",
publisher = "Elsevier",

}

RIS - Lataa

TY - JOUR

T1 - Improving the Delivery Cycle: A Multiple-Case Study of the Toolchains in Finnish Software Intensive Enterprises

AU - Mäkinen, Simo

AU - Leppänen, Marko

AU - Kilamo, Terhi

AU - Mattila, Anna-Liisa

AU - Laukkanen, Eero

AU - Pagels, Max

AU - Männistö, Tomi

PY - 2016/12

Y1 - 2016/12

N2 - Context: Software companies seek to gain benefit from agile development approaches in order to meet evolving market needs without losing their innovative edge. Agile practices emphasize frequent releases with the help of an automated toolchain from code to delivery.Objective: We investigate, which tools are used in software delivery, what are the reasons omitting certain parts of the toolchain and what implications toolchains have on how rapidly software gets delivered to customers.Method: We present a multiple-case study of the toolchains currently in use in Finnish software-intensive organizations interested in improving their delivery frequency. We conducted qualitative semi-structured interviews in 18 case organizations from various software domains. The interviewees were key representatives of their organization, considering delivery activities.Results: Commodity tools, such as version control and continuous integration, were used in almost every organization. Modestly used tools, such as UI testing and performance testing, were more distinctly missing from some organizations. Uncommon tools, such as artifact repository and acceptance testing, were used only in a minority of the organizations. Tool usage is affected by the state of current workflows, manual work and relevancy of tools. Organizations whose toolchains were more automated and contained fewer manual steps were able to deploy software more rapidly.Conclusions: There is variety in the need for tool support in different development steps as there are domain-specific differences in the goals of the case organizations. Still, a well-founded toolchain supports speedy delivery of new software.

AB - Context: Software companies seek to gain benefit from agile development approaches in order to meet evolving market needs without losing their innovative edge. Agile practices emphasize frequent releases with the help of an automated toolchain from code to delivery.Objective: We investigate, which tools are used in software delivery, what are the reasons omitting certain parts of the toolchain and what implications toolchains have on how rapidly software gets delivered to customers.Method: We present a multiple-case study of the toolchains currently in use in Finnish software-intensive organizations interested in improving their delivery frequency. We conducted qualitative semi-structured interviews in 18 case organizations from various software domains. The interviewees were key representatives of their organization, considering delivery activities.Results: Commodity tools, such as version control and continuous integration, were used in almost every organization. Modestly used tools, such as UI testing and performance testing, were more distinctly missing from some organizations. Uncommon tools, such as artifact repository and acceptance testing, were used only in a minority of the organizations. Tool usage is affected by the state of current workflows, manual work and relevancy of tools. Organizations whose toolchains were more automated and contained fewer manual steps were able to deploy software more rapidly.Conclusions: There is variety in the need for tool support in different development steps as there are domain-specific differences in the goals of the case organizations. Still, a well-founded toolchain supports speedy delivery of new software.

KW - Continuous deployment

KW - Continuous delivery

KW - Software development tools

KW - Deployment pipeline

KW - Agile software development

U2 - 10.1016/j.infsof.2016.09.001

DO - 10.1016/j.infsof.2016.09.001

M3 - Article

VL - 80

SP - 175

EP - 194

JO - Information and Software Technology

JF - Information and Software Technology

SN - 0950-5849

ER -

ID: 7312540