Agile Methodologies: Organizational Adoption Motives, Tailoring, and Performance
Published in Journal of Computer Information Systems, 2018
John F. Tripp, Deborah J. Armstrong
Agile methodologies have become widely popular since the publication of the agile manifesto in 2001 [39]. While various methodologies (e.g., extreme programming (XP) [2], scrum [33], feature-driven development (FDD) [29], and lean software development (LSD)) [30] have claimed the designation of “agile,” they advocate significantly different sets of agile practices. Agile practices are software development tasks or activities that are used to implement the agile method’s principles and values. Differences between the practices defined in each method are to be expected, as each method emerged from a different context, with somewhat different goals. For example, scrum [33] is an agile method that focuses primarily on managing project team tasks through practices such as a daily standup meeting, iteration planning, and delivery in short sprints.1In agile software development, work is contained in a regular, repeatable work cycle, known as a sprint or iteration. In contrast, XP [2] is an agile method that advocates practices that are focused on quality and software engineering techniques (e.g., pair programming, unit testing).