Loading [MathJax]/extensions/tex2jax.js

What Makes Agile Software Development Agile

Publikation: Beitrag in FachzeitschriftArtikelForschungPeer-Review

Autorschaft

  • Marco Kuhrmann
  • Paolo Tell
  • Regina Hebig
  • Jil Klünder
  • Kurt Schneider

Organisationseinheiten

Externe Organisationen

  • Universität Passau
  • IT University of Copenhagen
  • Chalmers University of Technology
  • Hochschule Reutlingen
  • FOM Hochschule für Oekonomie & Management gemeinnützige GmbH Essen
  • University of Tartu
  • Universität Innsbruck
  • Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)
  • Auckland University of Technology
  • Makerere University
  • Portland State University
  • University of Limerick
  • Bilkent University
  • Universidad de Costa Rica
  • Universidad Nacional de Tres de Febrero (UNTREF)
  • University of Otago
  • Technische Universität Clausthal
  • University of Calgary
  • Orta Dogu Technical University
  • Dublin City University
  • Dundalk Institute of Technology
  • Universität Kastilien-La Mancha
  • Pontifícia Universidade Católica do Rio de Janeiro (PUC-Rio)
  • Universidade Federal do Amazonas
  • Pontificia Universidade Catolica do Rio Grande do Sul
  • Technische Universität München (TUM)
  • Ataturk University
  • University of Bari
  • HSE University
  • University of Southern Denmark
  • Western Norway University of Applied Sciences (HVL)
  • Fraunhofer-Einrichtung Entwurfstechnik Mechatronik IEM
  • Victoria University of Wellington
  • École polytechnique de Montréal
  • Universität Paderborn
  • Technische Universität Wien (TUW)
  • Universidad de Chile
  • Lero The Irish Software Engineering Research Centre

Details

OriginalspracheEnglisch
Seiten (von - bis)3523-3539
Seitenumfang17
FachzeitschriftIEEE Transactions on Software Engineering
Jahrgang48
Ausgabenummer9
PublikationsstatusVeröffentlicht - 26 Juli 2021

Abstract

Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

ASJC Scopus Sachgebiete

Zitieren

What Makes Agile Software Development Agile. / Kuhrmann, Marco; Tell, Paolo; Hebig, Regina et al.
in: IEEE Transactions on Software Engineering, Jahrgang 48, Nr. 9, 26.07.2021, S. 3523-3539.

Publikation: Beitrag in FachzeitschriftArtikelForschungPeer-Review

Kuhrmann, M, Tell, P, Hebig, R, Klünder, J, Munch, J, Linssen, O, Pfahl, D, Felderer, M, Prause, C, Macdonell, S, Nakatumba-Nabende, J, Raffo, D, Beecham, S, Tuzun, E, Lopez, G, Paez, N, Fontdevila, D, Licorish, S, Kupper, S, Ruhe, G, Knauss, E, Ozcan-Top, O, Clarke, P, Mc Caffery, FH, Genero, M, Vizcaino, A, Piattini, M, Kalinowski, M, Conte, T, Prikladnicki, R, Krusche, S, Coskuncay, A, Scott, E, Calefato, F, Pimonova, S, Pfeiffer, RH, Pagh Schultz, U, Heldal, R, Fazal-Baqaie, M, Anslow, C, Nayebi, M, Schneider, K, Sauer, S, Winkler, D, Biffl, S, Bastarrica, C & Richardson, I 2021, 'What Makes Agile Software Development Agile', IEEE Transactions on Software Engineering, Jg. 48, Nr. 9, S. 3523-3539. https://doi.org/10.1109/TSE.2021.3099532
Kuhrmann, M., Tell, P., Hebig, R., Klünder, J., Munch, J., Linssen, O., Pfahl, D., Felderer, M., Prause, C., Macdonell, S., Nakatumba-Nabende, J., Raffo, D., Beecham, S., Tuzun, E., Lopez, G., Paez, N., Fontdevila, D., Licorish, S., Kupper, S., ... Richardson, I. (2021). What Makes Agile Software Development Agile. IEEE Transactions on Software Engineering, 48(9), 3523-3539. https://doi.org/10.1109/TSE.2021.3099532
Kuhrmann M, Tell P, Hebig R, Klünder J, Munch J, Linssen O et al. What Makes Agile Software Development Agile. IEEE Transactions on Software Engineering. 2021 Jul 26;48(9):3523-3539. doi: 10.1109/TSE.2021.3099532
Kuhrmann, Marco ; Tell, Paolo ; Hebig, Regina et al. / What Makes Agile Software Development Agile. in: IEEE Transactions on Software Engineering. 2021 ; Jahrgang 48, Nr. 9. S. 3523-3539.
Download
@article{ab5bdc40f85643b48cc316e01691705f,
title = "What Makes Agile Software Development Agile",
abstract = "Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.",
keywords = "Agile Software Development, Collaboration, Companies, Data collection, Hybrid Development Methods, Instruments, Market research, Software, Software Development, Software Process, Standards, Survey Research, software development, hybrid development methods, Agile software development, survey research, software process",
author = "Marco Kuhrmann and Paolo Tell and Regina Hebig and Jil Kl{\"u}nder and Jurgen Munch and Oliver Linssen and Dietmar Pfahl and Michael Felderer and Christian Prause and Steve Macdonell and Joyce Nakatumba-Nabende and David Raffo and Sarah Beecham and Eray Tuzun and Gustavo Lopez and Nicolas Paez and Diego Fontdevila and Sherlock Licorish and Steffen Kupper and Guenther Ruhe and Eric Knauss and Ozden Ozcan-Top and Paul Clarke and {Mc Caffery}, {Fergal Hugh} and Marcela Genero and Aurora Vizcaino and Mario Piattini and Marcos Kalinowski and Tayana Conte and Rafael Prikladnicki and Stephan Krusche and Ahmet Coskuncay and Ezequiel Scott and Fabio Calefato and Svetlana Pimonova and Pfeiffer, {Rolf Helge} and {Pagh Schultz}, Ulrik and Rogardt Heldal and Masud Fazal-Baqaie and Craig Anslow and Maleknaz Nayebi and Kurt Schneider and Stefan Sauer and Dietmar Winkler and Stefan Biffl and Cecilia Bastarrica and Ita Richardson",
note = "Publisher Copyright: {\textcopyright} 1976-2012 IEEE.",
year = "2021",
month = jul,
day = "26",
doi = "10.1109/TSE.2021.3099532",
language = "English",
volume = "48",
pages = "3523--3539",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
number = "9",

}

Download

TY - JOUR

T1 - What Makes Agile Software Development Agile

AU - Kuhrmann, Marco

AU - Tell, Paolo

AU - Hebig, Regina

AU - Klünder, Jil

AU - Munch, Jurgen

AU - Linssen, Oliver

AU - Pfahl, Dietmar

AU - Felderer, Michael

AU - Prause, Christian

AU - Macdonell, Steve

AU - Nakatumba-Nabende, Joyce

AU - Raffo, David

AU - Beecham, Sarah

AU - Tuzun, Eray

AU - Lopez, Gustavo

AU - Paez, Nicolas

AU - Fontdevila, Diego

AU - Licorish, Sherlock

AU - Kupper, Steffen

AU - Ruhe, Guenther

AU - Knauss, Eric

AU - Ozcan-Top, Ozden

AU - Clarke, Paul

AU - Mc Caffery, Fergal Hugh

AU - Genero, Marcela

AU - Vizcaino, Aurora

AU - Piattini, Mario

AU - Kalinowski, Marcos

AU - Conte, Tayana

AU - Prikladnicki, Rafael

AU - Krusche, Stephan

AU - Coskuncay, Ahmet

AU - Scott, Ezequiel

AU - Calefato, Fabio

AU - Pimonova, Svetlana

AU - Pfeiffer, Rolf Helge

AU - Pagh Schultz, Ulrik

AU - Heldal, Rogardt

AU - Fazal-Baqaie, Masud

AU - Anslow, Craig

AU - Nayebi, Maleknaz

AU - Schneider, Kurt

AU - Sauer, Stefan

AU - Winkler, Dietmar

AU - Biffl, Stefan

AU - Bastarrica, Cecilia

AU - Richardson, Ita

N1 - Publisher Copyright: © 1976-2012 IEEE.

PY - 2021/7/26

Y1 - 2021/7/26

N2 - Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

AB - Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

KW - Agile Software Development

KW - Collaboration

KW - Companies

KW - Data collection

KW - Hybrid Development Methods

KW - Instruments

KW - Market research

KW - Software

KW - Software Development

KW - Software Process

KW - Standards

KW - Survey Research

KW - software development

KW - hybrid development methods

KW - Agile software development

KW - survey research

KW - software process

UR - http://www.scopus.com/inward/record.url?scp=85112653399&partnerID=8YFLogxK

U2 - 10.1109/TSE.2021.3099532

DO - 10.1109/TSE.2021.3099532

M3 - Article

AN - SCOPUS:85112653399

VL - 48

SP - 3523

EP - 3539

JO - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

IS - 9

ER -

Von denselben Autoren