Investigating Impact of Business Risk on Requirements Selection Decisions

In market-driven software product development, requirements that can potentially go into a product or a product release represent different kinds of investments. Requirements differ in the type of value that they provide and level of risk associated to investing in them. In this paper we investigate how business risk associated with different requirement types is considered by the decision makers and how it affects requirement selection decisions. The results of the conducted case study indicate that due to lacking methods for handling the requirements business risk, requirements with low level of risk are preferred over other type of requirements such as innovations and architectural improvements.

[1]  A. Andrews,et al.  4 Requirements Prioritization , .

[2]  Anders Wall,et al.  A Method for Balancing Short- and Long-Term Investments: Quality vs. Features , 2008, 2008 34th Euromicro Conference Software Engineering and Advanced Applications.

[3]  Aybüke Aurum,et al.  When Product Managers Gamble with Requirements: Attitudes to Value and Risk , 2009, REFSQ.

[4]  Ian Sommerville,et al.  Software Engineering, 6. Auflage , 2001 .

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

[6]  Barry W. Boehm,et al.  An Initial Theory of Value-Based Software Engineering , 2006, Value-Based Software Engineering.

[7]  Harry M. Markowitz,et al.  Foundations of Portfolio Theory , 1991 .

[8]  Des Greer,et al.  Quantitative studies in software release planning under risk and resource constraints , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[9]  Björn Regnell,et al.  Challenges in Market-Driven Requirements Engineering - an Industrial Interview Study , 2002 .

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

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

[12]  Michel Benaroch,et al.  Managing Information Technology Investment Risk: A Real Options Perspective , 2002, J. Manag. Inf. Syst..

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

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

[15]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[16]  Tony Gorschek,et al.  Social networks in software process improvement , 2010 .

[17]  Marjo Kauppinen,et al.  Linking the business view to requirements engineering: long-term product planning by roadmapping , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[18]  Tony Gorschek,et al.  Requirements engineering: In search of the dependent variables , 2008, Inf. Softw. Technol..

[19]  Claes Wohlin,et al.  Criteria for Selecting Software Requirements to Create Product Value: An Industrial Empirical Study , 2006, Value-Based Software Engineering.

[20]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

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

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

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

[24]  Tony Gorschek,et al.  The impact of agile principles on market-driven software product development , 2010, J. Softw. Maintenance Res. Pract..