Rigorous Support for Flexible Planning of Product Releases - A Stakeholder-Centric Approach and Its Initial Evaluation

This paper addresses the problem of product release planning in iterative product development. We propose a method which combines decision, process, and tool support. The method, which is called SCERP, facilitates the active involvement of stakeholders in the different stages of the planning process. SCERP is flexible in the number of stakeholders involved, in the number of releases, in the number and definition of planning criteria, and in the selection of the best plan out of a set of optimized alternatives. A proof-of-concept of the method is given by a case study of release planning for a tool called Agilefant, which is developed with a process partially based on Scrum. The benefits of the method as demonstrated by the case study are: (i) better decisions by the product manager by relying on more objective information, (ii) more transparency of release decisions, and (iii) efficient tool support accompanying the whole process.

[1]  Günther Ruhe,et al.  A systematic approach for solving the wicked problem of software release planning , 2007, Soft Comput..

[2]  Tsun Chow,et al.  A survey study of critical success factors in agile software projects , 2008, J. Syst. Softw..

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

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

[5]  Ho-Won Jung,et al.  Optimizing Value and Cost in Requirements Analysis , 1998, IEEE Softw..

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

[7]  Günther Ruhe,et al.  Intelligent Support for Software Release Planning , 2004, PROFES.

[8]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[9]  Casper Lassenius,et al.  An experience in combining flexibility and control in a small company's software product development process , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[10]  Sjaak Brinkkemper,et al.  Software product release planning through optimization and what-if analysis , 2008, Inf. Softw. Technol..

[11]  Christof Ebert,et al.  The impacts of software product management , 2007, J. Syst. Softw..

[12]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[13]  George Wright,et al.  The Delphi technique as a forecasting tool: issues and analysis , 1999 .

[14]  Aybüke Aurum,et al.  Understanding Decision-Making in Agile Software Development: A Case-study , 2008, 2008 34th Euromicro Conference Software Engineering and Advanced Applications.

[15]  Jane Cleland-Huang,et al.  The incremental funding method: data-driven software development , 2004, IEEE Software.

[16]  N. Kano,et al.  Attractive Quality and Must-Be Quality , 1984 .

[17]  Günther Ruhe,et al.  Release planning process improvement - an industrial case study , 2006, Softw. Process. Improv. Pract..

[18]  Victor J. Rayward-Smith,et al.  The next release problem , 2001, Inf. Softw. Technol..

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

[20]  Ken Schwaber.  The Enterprise and Scrum , 2007 .

[21]  Galal H. Galal-Edeen,et al.  Stakeholder identification in the requirements engineering process , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[22]  Alan M. Davis,et al.  Just Enough Requirements Management: Where Software Development Meets Marketing , 2005 .

[23]  Kjetil Moløkken-Østvold,et al.  Using planning poker for combining expert estimates in software projects , 2008, J. Syst. Softw..

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