An Approach for Prioritizing Agile Practices for Adaptation

Agile software development approaches offer a strong alternative to the traditional plan-driven methodologies that have not been able to warrant successfulness of the software projects. However, the move toward Agile is often hampered by the wealth of alternative practices that are accompanied by numerous success or failure stories. Clearly, the formal methods for choosing most suitable practices are lacking. In this chapter, we present an overview of this problem and propose an approach for prioritization of available practices in accordance to the particular circumstances. The proposal combines ideas from Analytic Hierarchy Process (AHP) decision-making technique, cost-value analysis, and Rule-Description-Practice (RDP) technique. Assumption that such approach could facilitate the Agile adaptation process was supported by the case study of the approach illustrating the process of choosing most suitable Agile practices within a real-life project.

[1]  Ron Jeffries,et al.  Extreme Programming Installed , 2000 .

[2]  Brian Henderson-Sellers,et al.  Comparison of Method Chunks and Method Fragments for Situational Method Engineering , 2008 .

[3]  Frank Keenan,et al.  Agile process tailoring and problem analysis (APTLY) , 2004, Proceedings. 26th International Conference on Software Engineering.

[4]  Jerry Drobka,et al.  Piloting XP on four mission-critical projects , 2004, IEEE Software.

[5]  Dietmar Pfahl,et al.  Quantitative WinWin: a new method for decision support in requirements negotiation , 2002, SEKE '02.

[6]  Peng Xu,et al.  How extreme does extreme programming have to be? Adapting XP practices to large-scale projects , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[7]  Pekka Abrahamsson,et al.  New directions on agile methods: a comparative analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[8]  Donald Firesmith,et al.  The OPEN process framework , 2001 .

[9]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[10]  Walter Ambu,et al.  Extreme Programming at Work , 2003, XP.

[11]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

[12]  Brian Henderson-Sellers,et al.  The open process framework : an introduction , 2002 .

[13]  Mehdi Mirakhorli,et al.  RDP Technique: Take a Different Look at XP for Adoption , 2008 .

[14]  Asif Qumer Gill,et al.  Measuring agility and adaptibility of agile methods: A 4 dimensional analytical tool , 2006 .

[15]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[16]  Amr Elssamadisy.  XP On A Large Project – A Developer’s View , 2001 .

[17]  James Grenning,et al.  Launching Extreme Programming at a Process-Intensive Company , 2001, IEEE Softw..

[18]  Alistair Cockburn,et al.  Agile Software Development: The Cooperative Game (2nd Edition) (Agile Software Development Series) , 2006 .

[19]  T. Saaty.  Fundamentals of the Analytic Hierarchy Process , 2001 .

[20]  Brian Henderson-Sellers,et al.  Construction of an Agile Software Product-Enhancement Process by Using an Agile Software Solution Framework (ASSF) and Situational Method Engineering , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[21]  Des Greer,et al.  Software release planning: an evolutionary and iterative approach , 2004, Inf. Softw. Technol..

[22]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

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

[24]  Barry W. Boehm,et al.  Empirical Findings in Agile Methods , 2002, XP/Agile Universe.

[25]  Lucas Layman,et al.  Exploring extreme programming in context: an industrial case study , 2004, Agile Development Conference.

[26]  B. Dwolatzky,et al.  Agile Methodologies Selection Toolbox , 2007, International Conference on Software Engineering Advances (ICSEA 2007).

[27]  Ken Frazer,et al.  Review of "Managing software requirements, a use case approach by Dean Leffingwell and Don Widrig." Addison-Wesley 2003 , 2004, SOEN.

[28]  Iman Attarzadeh,et al.  New direction in project management success: Base on smart methodology selection , 2008, 2008 International Symposium on Information Technology.

[29]  Marjo Kauppinen,et al.  Empirical Evaluation of Two Requirements Prioritization Methods in Product Development Projects , 2004, EuroSPI.

[30]  Thomas L. Saaty.  Multi-decisions decision-making: In addition to wheeling and dealing, our national political bodies need a formal approach for prioritization , 2007, Math. Comput. Model..

[31]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[32]  Alistair Cockburn,et al.  Selecting a Project 's Methodology , 2000, IEEE Softw..

[33]  Mehmet N. Aydin,et al.  An Agile Information Systems Development Method in Use , 2004 .

[34]  Claes Wohlin,et al.  An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..