The Risks of Agile Software Development : Learning from Adopters. / Elbanna, Amany; Sarker, Suprateek.

In: IEEE Software, Vol. 33, No. 5, 11.11.2015, p. 72-79.

Research output: Contribution to journalArticlepeer-review

E-pub ahead of print

Standard

The Risks of Agile Software Development : Learning from Adopters. / Elbanna, Amany; Sarker, Suprateek.

In: IEEE Software, Vol. 33, No. 5, 11.11.2015, p. 72-79.

Research output: Contribution to journalArticlepeer-review

Harvard

APA

Vancouver

Author

BibTeX

@article{355d9cae198d49f58a8c1c8b871aacf0,
title = "The Risks of Agile Software Development: Learning from Adopters",
abstract = "Agile software development (ASD) emerged as a result of widespread professional discontent with traditional approaches, the high failure rates associated with software development projects, and most importantly, the need for speedy responsive delivery of software particularly for Internet businesses. Today, ASD approaches are embraced by many practitioners, and often extolled by commentators as being {\textquoteleft}faster, better, cheaper{\textquoteright} approach to software development. However, a recent high profile failure of an ASD project and the discontinuance of the use of ASD practices in a software company have drawn attention to possible risks associated with ASD. Before we can manage such risks, an important first step is to identify the risks and understand why these risks arise in the ASD context. In this paper, we offer insights derived from the examination of ASD practices in 28 organizations. Based on 112 interviews conducted in these organizations and further 25 interviews conducted with agile software development contractors (developers and project managers) and consultants, we unearthed key risk factors related to ASD practice that need to be carefully managed to achieve desired project outcomes. ",
keywords = "Agile software development, software risk management, software development methods, technical debt",
author = "Amany Elbanna and Suprateek Sarker",
year = "2015",
month = nov,
day = "11",
doi = "10.1109/ms.2015.150",
language = "English",
volume = "33",
pages = "72--79",
journal = "IEEE Software",
issn = "0740-7459",
publisher = "IEEE Computer Society",
number = "5",

}

RIS

TY - JOUR

T1 - The Risks of Agile Software Development

T2 - Learning from Adopters

AU - Elbanna, Amany

AU - Sarker, Suprateek

PY - 2015/11/11

Y1 - 2015/11/11

N2 - Agile software development (ASD) emerged as a result of widespread professional discontent with traditional approaches, the high failure rates associated with software development projects, and most importantly, the need for speedy responsive delivery of software particularly for Internet businesses. Today, ASD approaches are embraced by many practitioners, and often extolled by commentators as being ‘faster, better, cheaper’ approach to software development. However, a recent high profile failure of an ASD project and the discontinuance of the use of ASD practices in a software company have drawn attention to possible risks associated with ASD. Before we can manage such risks, an important first step is to identify the risks and understand why these risks arise in the ASD context. In this paper, we offer insights derived from the examination of ASD practices in 28 organizations. Based on 112 interviews conducted in these organizations and further 25 interviews conducted with agile software development contractors (developers and project managers) and consultants, we unearthed key risk factors related to ASD practice that need to be carefully managed to achieve desired project outcomes.

AB - Agile software development (ASD) emerged as a result of widespread professional discontent with traditional approaches, the high failure rates associated with software development projects, and most importantly, the need for speedy responsive delivery of software particularly for Internet businesses. Today, ASD approaches are embraced by many practitioners, and often extolled by commentators as being ‘faster, better, cheaper’ approach to software development. However, a recent high profile failure of an ASD project and the discontinuance of the use of ASD practices in a software company have drawn attention to possible risks associated with ASD. Before we can manage such risks, an important first step is to identify the risks and understand why these risks arise in the ASD context. In this paper, we offer insights derived from the examination of ASD practices in 28 organizations. Based on 112 interviews conducted in these organizations and further 25 interviews conducted with agile software development contractors (developers and project managers) and consultants, we unearthed key risk factors related to ASD practice that need to be carefully managed to achieve desired project outcomes.

KW - Agile software development

KW - software risk management

KW - software development methods

KW - technical debt

U2 - 10.1109/ms.2015.150

DO - 10.1109/ms.2015.150

M3 - Article

VL - 33

SP - 72

EP - 79

JO - IEEE Software

JF - IEEE Software

SN - 0740-7459

IS - 5

ER -