Source-linked AI summary
Limitations of Agile Software Processes
Dan Turk, Robert France, Bernhard Rumpe
TL;DR
Evidence on agile-process suitability is often anecdotal, making appropriateness difficult to assess across application domains and development environments. The paper analytically examines assumptions in several agile processes and identifies project contexts where their application may be problematic.
Problem
Agile-process suitability across application domains and development environments is often assessed from anecdotal experience rather than systematic evidence.
Method
The paper analytically examines assumptions underlying XP, Scrum, Agile Unified Process, Agile Modeling, and Agile Alliance principles, with limited support from a few XP projects.
Results
The analysis identifies limitations of published agile processes concerning the types of projects in which their application may be problematic.
Takeaways & Limitations
Assessing agile processes requires considering project characteristics and the assumptions underlying the particular process rather than treating agile processes as uniform.
Takeaways & Limitations
Current agile quality-control mechanisms have not proven adequate to assure safety-critical software users that products are safe.
Abstract
from arXiv · showhide
Software developers and project managers are struggling to assess the appropriateness of agile processes to their development environments. This paper identifies limitations that apply to many of the published agile processes in terms of the types of projects in which their application may be problematic.