A conceptual model and process for client-driven agile requirements prioritization

Continuous customer-centric requirements reprioritization is essential in successfully performing agile software development. Yet, in the agile RE literature, very little is known about how agile reprioritization happens in practice. Generic conceptual models about this process are missing, which in turn, makes it difficult for both practitioners and researchers to reason about requirements decision-making at inter-iteration time. This paper presents a Grounded Theory study on agile requirements prioritization methods to yield a conceptual model for understanding the inter-iteration prioritization process in terms of inputs and outcomes. The latter is derived by using qualitative empirical data, published earlier by other authors. Such a conceptual model makes explicit the concepts that are used tacitly in different agile requirements prioritization methods and can be used for structuring future empirical investigations about this topic.

[1]  W. R. Howard Agile Project Management: Creating Innovative Products , 2010 .

[2]  Sanjiv Augustine,et al.  Managing Agile Projects , 2005 .

[3]  Karl E. Wiegers First Things First: Prioritizing Requirements , 1999 .

[4]  K. Charmaz,et al.  Constructing Grounded Theory: A practical guide through qualitative analysis Kathy Charmaz Constructing Grounded Theory: A practical guide through qualitative analysis Sage 224 £19.99 0761973532 0761973532 [Formula: see text]. , 2006, Nurse researcher.

[5]  Craig Larman,et al.  Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum , 2008 .

[6]  A. Clarke Situational Analysis: Grounded Theory After the Postmodern Turn , 2005 .

[7]  Pamela Jordan Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[8]  Klaas Sikkel,et al.  Value Creation by Agile Projects: Methodology or Mystery? , 2009, PROFES.

[9]  Jeff Patton Finding the forest in the trees , 2005, OOPSLA '05.

[10]  Jeff Patton Ambiguous Business Value Harms Software Products , 2008, IEEE Software.

[11]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..

[12]  Claes Wohlin,et al.  A product management challenge: Creating software product value through requirements selection , 2008, J. Syst. Archit..

[13]  B. Glaser Basics of Grounded Theory Analysis: Emergence Vs. Forcing , 1992 .

[14]  Philippe Kruchten,et al.  Agile project management , 2021, Project Management, Planning and Control.

[15]  Wolf-Gideon Bleek,et al.  Agile Softwareentwicklung - Werte, Konzepte und Methoden , 2008 .

[16]  Sjaak Brinkkemper,et al.  Integrated Requirement Selection and Scheduling for the Release Planning of a Software Product , 2007, REFSQ.

[17]  Claes Wohlin,et al.  A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case , 2009, J. Syst. Softw..

[18]  Mike Cohn,et al.  Incorporating Learning and Expected Cost of Change in Prioritizing Features on Agile Projects , 2006, XP.

[19]  Claes Wohlin,et al.  Pair-wise comparisons versus planning game partitioning—experiments on requirements prioritisation techniques , 2007, Empirical Software Engineering.

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

[21]  M. Bohanec,et al.  The Analytic Hierarchy Process , 2004 .

[22]  John Hunt,et al.  Agile software construction , 2005 .

[23]  Jean Tabaka,et al.  Collaboration Explained: Facilitation Skills for Software Project Leaders , 2006 .

[24]  Mike Cohn,et al.  Agile Estimating and Planning , 2005 .

[25]  Beatrice Alenljung,et al.  Portraying the practice of decision-making in requirements engineering: a case of large scale bespoke development , 2008, Requirements Engineering.

[26]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[27]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[28]  C Berger,et al.  KANO’S METHODS FOR UNDERSTANDING CUSTOMER-DEFINED QUALITY , 1993 .

[29]  Martin Lippert,et al.  eXtreme Programming in Action: Practical Experiences From Real World Projects , 2002 .