University of Hertfordshire

From the same journal

By the same authors

Standard

When Agile Is Not Good Enough : an initial attempt at understanding how to make the right decision. / Veneziano, Vito; W. Rainer, Austen; Haider, Sheraz.

In: ArXiv, 22.02.2014.

Research output: Contribution to journalArticle

Harvard

APA

Vancouver

Author

Bibtex

@article{7a5aee58832c4ae091300bd0db40e47f,
title = "When Agile Is Not Good Enough: an initial attempt at understanding how to make the right decision",
abstract = "Along the years, Agile has attracted not only the praises of a broad range of enthusiast software developers, but also the blames of a less noisy flight of critical practitioners. Either way, support or relinquishment of Agile seems based more on an emotional attitude than on a critical, well-informed decision making process. In this paper, the dual nature of such criticism is discussed, and, by identifying and classifying most of the arguments against Agile within a critical taxonomy of risk factors, a decisional model and a tool based on such a taxonomy are consequently proposed for supporting software engineers and other stakeholders in the decision-making about whether or not to go Agile. The tool, which is freely available online, comes with a set of guidelines and it aims at encouraging the community of software developers to contribute on further assessing the potential as well as the criticalities of Agile Methods.",
keywords = "cs.SE, cs.CY, D.2.9; K.6",
author = "Vito Veneziano and {W. Rainer}, Austen and Sheraz Haider",
year = "2014",
month = feb,
day = "22",
language = "English",
journal = "ArXiv",

}

RIS

TY - JOUR

T1 - When Agile Is Not Good Enough

T2 - an initial attempt at understanding how to make the right decision

AU - Veneziano, Vito

AU - W. Rainer, Austen

AU - Haider, Sheraz

PY - 2014/2/22

Y1 - 2014/2/22

N2 - Along the years, Agile has attracted not only the praises of a broad range of enthusiast software developers, but also the blames of a less noisy flight of critical practitioners. Either way, support or relinquishment of Agile seems based more on an emotional attitude than on a critical, well-informed decision making process. In this paper, the dual nature of such criticism is discussed, and, by identifying and classifying most of the arguments against Agile within a critical taxonomy of risk factors, a decisional model and a tool based on such a taxonomy are consequently proposed for supporting software engineers and other stakeholders in the decision-making about whether or not to go Agile. The tool, which is freely available online, comes with a set of guidelines and it aims at encouraging the community of software developers to contribute on further assessing the potential as well as the criticalities of Agile Methods.

AB - Along the years, Agile has attracted not only the praises of a broad range of enthusiast software developers, but also the blames of a less noisy flight of critical practitioners. Either way, support or relinquishment of Agile seems based more on an emotional attitude than on a critical, well-informed decision making process. In this paper, the dual nature of such criticism is discussed, and, by identifying and classifying most of the arguments against Agile within a critical taxonomy of risk factors, a decisional model and a tool based on such a taxonomy are consequently proposed for supporting software engineers and other stakeholders in the decision-making about whether or not to go Agile. The tool, which is freely available online, comes with a set of guidelines and it aims at encouraging the community of software developers to contribute on further assessing the potential as well as the criticalities of Agile Methods.

KW - cs.SE

KW - cs.CY

KW - D.2.9; K.6

M3 - Article

JO - ArXiv

JF - ArXiv

ER -