The Challenge of Release Planning Visible But Not Seen

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]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

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

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

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

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

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

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

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

[9]  Jeff Conklin,et al.  Dialogue Mapping: Building Shared Understanding of Wicked Problems , 2005 .

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

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

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

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

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

[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]  Jay F. Nunamaker,et al.  Principles for effective virtual teamwork , 2009, CACM.

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

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

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

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

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

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

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

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

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

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

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

[28]  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..

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

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

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

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

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

[34]  Yochai Benkler,et al.  The wealth of networks: how social production transforms markets and freedom , 2006 .

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

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

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

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

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

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

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

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

[43]  T. Saaty,et al.  The Analytic Hierarchy Process , 1985 .

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

[45]  Ronald L. Rivest,et al.  Introduction to Algorithms , 1990 .

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

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

[48]  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.

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

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

[51]  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).

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

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

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

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

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

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

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

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

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