The challenge of release planning

Size and complexity of today's software products are continuously growing. This has made it increasingly difficult to decide which features shall be implemented in a product's next version. Consequently, release planning, the process of planning for the next release of an evolving product has been recognized as a wicked problem. Existing studies on wicked problems suggest that it would be too simple to deal with them with intelligence gathering, linear thinking and rational decision making. Yet, it appears that this is precisely how many companies are currently trying to plan their forthcoming product releases. Although the characteristics of release planning challenges are visible and documented in the literature, is this challenge really seen? This paper reviews existing release planning practices introduced in the literature in order to understand the underlying assumptions they have been built on. The identified assumptions are then compared with reported release planning characteristics. As a result, the paper identifies the gap between the problem characteristics and the current solutions, and outlines conditions for more adequate release planning approaches to deal with release planning as complex wicked problems.

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

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

[3]  Hans-Jürgen Engelbrecht.  The wealth of networks: How social production transforms markets and freedom , 2006 .

[4]  Satyanarayana Parayitam,et al.  The interplay between cognitive- and affective conflict and cognition- and affect-based trust in influencing decision outcomes , 2009 .

[5]  Jock Given,et al.  The wealth of networks: How social production transforms markets and freedom , 2007, Inf. Econ. Policy.

[6]  Björn Regnell,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007, Inf. Softw. Technol..

[7]  Chun Wei Choo.  Sensemaking, Knowledge Creation, and Decision Making , 2002 .

[8]  K. Weick,et al.  Collective mind in organizations: Heedful interrelating on flight decks. , 1993 .

[9]  Anne Persson,et al.  Requirements Interdependencies: State of the Art and Future Challenges , 2005 .

[10]  Chun Wei Choo,et al.  The Strategic Management of Intellectual Capital and Organizational Knowledge , 2002 .

[11]  F. Burstein,et al.  Handbook on Decision Support Systems 1 , 2008 .

[12]  Pär Carlshamre,et al.  A usability perspective on requirements engineering : from methodology to product development , 2001 .

[13]  Björn Regnell,et al.  A market-driven requirements engineering process: Results from an industrial process improvement programme , 1998, Requirements Engineering.

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

[15]  Inge van de Weerd,et al.  Towards a Reference Framework for Software Product Management , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

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

[17]  Marjo Kauppinen,et al.  Requirements Prioritization Challenges in Practice , 2004, PROFES.

[18]  R. Mason,et al.  Challenging strategic planning assumptions : theory, cases, and techniques , 1981 .

[19]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

[20]  David A. Penny,et al.  An estimation-based management framework for enhancive maintenance in commercial software products , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[21]  Rudy Hirschheim,et al.  Four paradigms of information systems development , 1989, CACM.

[22]  Stefan Biffl,et al.  Stakeholder Value Proposition Elicitation and Reconciliation , 2006, Value-Based Software Engineering.

[23]  I. Janis.  Groupthink: Psychological Studies of Policy Decisions and Fiascoes , 1982 .

[24]  Nam P. Suh.  Design of Systems , 2007 .

[25]  Jay F. Nunamaker,et al.  Principles for effective virtual teamwork , 2009, CACM.

[26]  Rudy Hirschheim,et al.  A research agenda for future information systems development methodologies , 1992 .

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

[28]  K. Jehn.  A Multimethod Examination of the Benefits and Detriments of Intragroup Conflict , 1995 .

[29]  Kari Smolander,et al.  How Internationalization of a Product Changes Requirements Engineering Activities: An Exploratory Study , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[30]  RegnellBjörn,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007 .

[31]  Nancy C. Roberts,et al.  Wicked Problems and Network Approaches to Resolution , 2000 .

[32]  Donald C. Gause,et al.  Making Sense of Product Requirements , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[33]  Daniela E. Damian,et al.  RE challenges in multi-site software development organisations , 2003, Requirements Engineering.

[34]  R. Feldt,et al.  A systematic review on strategic release planning models , 2010, Inf. Softw. Technol..

[35]  Günther Ruhe,et al.  The Science and Practice of Software Release Planning , 2004 .

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

[37]  D. Morgan,et al.  Sociological Paradigms and Organizational Analysis. , 1983 .

[38]  Patrik Berander,et al.  Towards a Research Framework on Requirements Prioritization , 2006 .

[39]  Marjo Kauppinen,et al.  Linking business and requirements engineering: is solution planning a missing activity in software product companies? , 2009, Requirements Engineering.

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

[41]  Esa Sirkkunen,et al.  Social media. Introduction to the tools and processes of participatory economy , 2008 .

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

[43]  Jr. Uldarico Rex B. Dumdum,et al.  An approach to problem formulation in ill-structured situations in information systems development , 1993 .

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

[45]  Marjo Kauppinen,et al.  Suitability of requirements prioritization methods for market-driven software product development , 2006, Softw. Process. Improv. Pract..

[46]  Björn Regnell,et al.  Market-Driven Requirements Engineering for Software Products , 2005 .

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

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

[49]  Claes Wohlin,et al.  Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning , 2004, ICSE 2004.

[50]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.

[51]  Robert O. Briggs,et al.  Collaboration Engineering: Designing Repeatable Processes for High-Value Collaborative Tasks , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

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

[53]  Nick Boucart,et al.  Demystifying Release Definition: From Requirements Prioritization to Collaborative Value Quantification , 2009, REFSQ.

[54]  K. Weick.  FROM SENSEMAKING IN ORGANIZATIONS , 2021, The New Economic Sociology.

[55]  Ian I. Mitroff,et al.  Policy as Argument-A Logic for Ill-Structured Decision Problems , 1982 .

[56]  Tuure Tuunanen,et al.  A Contigency Model for Requirements Development , 2007, J. Assoc. Inf. Syst..

[57]  Linda Gorchels.  The Product Manager's Handbook: The Complete Product Management Resource , 2000 .

[58]  Nam P. Suh.  Design of Systems , 1997 .

[59]  Nicholas P. Vitalari,et al.  Structuring the requirements analysis process for information systems: a proposition viewpoint , 1992 .

[60]  Shahid Yusuf,et al.  From Creativity to Innovation , 2007 .

[61]  K. Weick.  Making Sense of the Organization , 2000 .

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

[63]  Günther Ruhe,et al.  Product Release Planning - Methods, Tools and Applications , 2010 .

[64]  Richard J. Boland,et al.  Decision Making and Sensemaking , 2008 .

[65]  Peter Checkland,et al.  From Optimizing to Learning: A Development of Systems Thinking for the 1990s , 1985 .

[66]  Matthias Jarke,et al.  Requirements engineering in 2001: (virtually) managing a changing reality , 1994, Softw. Eng. J..

[67]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .