Agile Software Development Methodologies: Survey of Surveys

Abstract

Agile software design and development methodologies have been gaining rigorous attention in the software engineering research community since their early introduction in the mid-nineties in addition to being highly adopted by the software development industry. In the last 15 years, an excessive number of research studies have been conducted on agile methods, a great number of notable methods have been proposed and various surveys have been presented by many researchers. In this study, the authors intend to conduct a literature survey study of the surveys of the different agile methodologies ranging from January 2000 to December 2015 using an intuitive research methodology called "Compare and Review" (CR). Furthermore, these survey papers were classified into four major categories according to their area of study. Additionally, the newly proposed agile methodologies that have not been addressed yet in any other literature review were reviewed and compared in terms of where the changes that they proposed lay on the SDLC.

Agility: The Need of an Hour for Software Industry

“…• This sort of programming advancement model requires gatherings at visit interims at enormous cost to clients [21].…”

“…• The venture may go toward another path if client agent does not have clear thought regarding the necessity [21].…”

“…The necessities will change tomorrow, so just do what's expected to meet the present prerequisites. Plan in XP is not a one-time thing but rather an all-the-time thing [21]. Metaphor: XP groups build up a typical vision of how the program functions, which we call the "illustration" or "Metaphor".…”

“…Occasional combination prompts major issues on a product venture. Most importantly, despite the fact that integration is basic to deliver great working code, the group is not rehearsed at it, and frequently it is appointed to individuals who are not familiar with the entire framework [21]. 40-Hour Work Week: Software engineers go home on time.…”

“…Build up a general model: The FDD strategy demands that groups apply the sufficient measure of input toward the beginning of the task so as to build an object procedure featuring the domain issue [21]. Demonstrating with FDD is time-boxed and community oriented.…”