[Paper Review] When Agile Is Not Good Enough: an initial attempt at understanding how to make the right decision

Vito Veneziano, Austen Rainer+1 more|arXiv (Cornell University)|Feb 22, 2014

Software Engineering Techniques and Practices5 references3 citations

TL;DR

This paper proposes a decisional model and tool to help software teams assess whether Agile methodologies are suitable for their context, based on a critical taxonomy of risk factors. By classifying arguments against Agile into structured risk categories, the framework enables informed, evidence-based decisions, with the tool publicly available to support community-driven evaluation of Agile's applicability and limitations.

ABSTRACT

Particularly over the last ten years, Agile has attracted not only the praises of a broad range of enthusiast software developers, but also the criticism of others. Either way, adoption or rejection of Agile seems sometimes to be based more on a questionable understanding than on a critical, well-informed decision making process. In this paper, the dual nature of the above criticism is discussed, and the arguments against Agile have been classified within a critical taxonomy of risk factors. A decisional model and tool based on such taxonomy are consequently proposed for supporting software engineers and other stakeholders in the decision-making about whether or not to use Agile. The tool, which is freely available online, comes with a set of guidelines: its purpose is to facilitate the community of software developers to contribute to further assessing the potential and the criticalities of Agile Methods.

Motivation & Objective

• To address the growing polarization around Agile adoption, where decisions are often based on ideology rather than critical evaluation.
• To identify and classify the core arguments against Agile into a structured, critical taxonomy of risk factors.
• To develop a decision-support tool that enables software engineers and stakeholders to evaluate whether Agile is appropriate for their specific context.
• To promote community-driven assessment of Agile's strengths and limitations through an open, extensible framework.
• To support informed decision-making by moving beyond binary Agile/non-Agile choices toward context-sensitive adoption strategies.

Proposed method

• The authors developed a critical taxonomy of risk factors derived from existing criticisms of Agile, categorizing them into structural, organizational, and technical dimensions.
• The taxonomy was used to design a decisional model that evaluates the compatibility of Agile with specific project and organizational contexts.
• A web-based tool was implemented to operationalize the model, allowing users to input project characteristics and receive recommendations based on risk factor alignment.
• The tool includes guidelines for interpreting results and encourages community contributions to refine and extend the risk factor classification.
• The framework integrates principles from software engineering and socio-technical systems theory to balance flexibility and rigor in decision-making.
• The model is designed to be extensible, allowing for future expansion as new risk factors emerge from empirical feedback.

Experimental results

Research questions

• RQ1 What are the primary arguments against Agile that are often overlooked or oversimplified in mainstream discourse?
• RQ2 How can the diverse criticisms of Agile be systematically categorized to support structured decision-making?
• RQ3 To what extent can a risk-based taxonomy improve the accuracy and transparency of Agile adoption decisions?
• RQ4 How can a decision-support tool based on such a taxonomy be designed to be both practical and extensible?
• RQ5 What role can community contributions play in refining and validating the risk factor classification over time?

Key findings

• The authors successfully developed a comprehensive taxonomy of risk factors that captures the dual nature of Agile criticism—both practical and philosophical.
• The decisional model enables stakeholders to evaluate Agile suitability by mapping project-specific characteristics to identified risk factors.
• The web-based tool, freely available online, provides actionable recommendations based on the taxonomy, enhancing transparency in Agile adoption decisions.
• The framework supports iterative improvement through community contributions, increasing its long-term validity and adaptability.
• The study demonstrates that Agile adoption decisions can be systematized and depoliticized using a risk-based, evidence-informed approach.
• The model shows potential for extension to other software development methodologies beyond Agile, enhancing its broader applicability.