Assessing an Organization's Capability to Effectively Implement Its Selected Agile Method(s): An Objectives, Principles, Strategies Approach

Agile methods provide an organization or a team with the flexibility to adopt a selected subset of principles and practices based on their culture, their values, and the types of systems that they develop. More specifically, every organization or team implements a customized agile method, tailored to better accommodate its needs. However, the extent to which a customized method supports the organizational objectives, i.e. the 'goodness' of that method, should be demonstrable. Existing agile assessment approaches focus on comparative analyses, or are limited in scope and application. In this research, we present a systematic, comprehensive approach to assessing the 'goodness' of agile methods. We examine an agile method based on (1) its adequacy, (2) the capability of the organization to support the adopted principles and practices specified by the method, and (3) the method's effectiveness. We employ the Objectives, Principles and Strategies (OPS) Framework to guide our assessment process. The Framework (a) specifies objectives of the agile philosophy, (b) identifies principles that support the objectives, (c) designates strategies that implement the principles, (d) defines linkages that relate objectives to principles, and principles to strategies, and (e) prescribes indicators for assessing the extent to which an organization supports the implementation and effectiveness of those strategies. The propagation of indicator values along the linkages provides a multi-level assessment view of the agile method. In this paper, we discuss our assessment approach and substantiation results.

[1]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[2]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[3]  Theodore D. Hellmann,et al.  Agile Testing: Past, Present, and Future -- Charting a Systematic Map of Testing in Agile Software Development , 2012, 2012 Agile Conference.

[4]  Shane Warden,et al.  The art of agile development , 2007 .

[5]  Mark C. Paulk,et al.  Capability Maturity Model for Software, Version 1.1 , 1993 .

[6]  James D. Arthur,et al.  A Structured Framework for Assessing the "Goodness" of Agile Methods , 2010, 2011 18th IEEE International Conference and Workshops on Engineering of Computer-Based Systems.

[7]  Laurie A. Williams,et al.  Driving Process Improvement via Comparative Agility Assessment , 2010, 2010 Agile Conference.

[8]  James D. Arthur,et al.  A disciplined approach to adopting agile practices: the agile adoption framework , 2007, Innovations in Systems and Software Engineering.

[9]  James D. Arthur,et al.  A structured approach to adopting agile practices: the agile adoption framework , 2007 .

[10]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[11]  W. Marsden I and J , 2012 .

[12]  Bonnie E. John Evidence-based practice in human-computer interaction and evidence maps , 2005, ACM SIGSOFT Softw. Eng. Notes.

[13]  James D. Arthur,et al.  A Methodology for Assessing Agile Software Development Methods , 2012, 2012 Agile Conference.

[14]  Reina Mori Research on Design Processes of Workshops for Learning , 2008 .

[15]  Asif Gill,et al.  An evaluation of the degree of agility in six agile methods and its applicability for method engineering , 2008, Inf. Softw. Technol..

[16]  Asif Qumer Gill,et al.  Agile adoption and improvement model , 2007 .

[17]  Scott W. Ambler,et al.  Agile modeling: effective practices for extreme programming and the unified process , 2002 .

[18]  Alistair Cockburn,et al.  Crystal Clear: A Human-Powered Methodology for Small Teams , 2004 .

[19]  James D. Arthur,et al.  A Framework for Assessing the Adequacy and Effectiveness of software development methodologies , 1991 .

[20]  James D. Arthur,et al.  Value-Driven Agile Adoption: Improving An Organization's Software Development Approach , 2008, SoMeT.

[21]  Ananth Srinivasan,et al.  Understanding Post-Adoptive Agile Usage -- An Exploratory Cross-Case Analysis , 2011, 2011 AGILE Conference.

[22]  Jeff Sutherland,et al.  Manifesto for Agile Software Development , 2013 .

[23]  Dave Ulrich,et al.  Capitalizing on capabilities. , 2004, Harvard business review.

[24]  Lucas Layman,et al.  Personality types, learning styles, and an agile approach to software engineering education , 2006, SIGCSE '06.

[25]  G. Melnik,et al.  A cross-program investigation of students' perceptions of agile methods , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[26]  Bjørnar Tessem,et al.  Human and social factors of software engineering: workshop summary , 2005, SOEN.

[27]  Muhammad Raza Ali Imparting effective software engineering education , 2006, SOEN.

[28]  Shvetha Soundararajan,et al.  A Methodology for assessing Agile Software Development Approaches , 2011, ArXiv.

[29]  Eric Braude Software Engineering: An Object-Oriented Perspective , 2000 .

[30]  Silvio Romero de Lemos Meira,et al.  Agile software product lines: a systematic mapping study , 2011, Softw. Pract. Exp..