Linking business and requirements engineering: is solution planning a missing activity in software product companies?

A strong link between strategy and product development is important, since companies need to select requirements for forthcoming releases. However, in practice, connecting requirements engineering (RE) and business planning is far from trivial. This paper describes the lessons learned from four software product companies that have recognized the need for more business-oriented long-term planning. The study was conducted using the action research approach. We identified five practices that seem to strengthen the link between business decisions and RE. These are (1) explicating the planning levels and time horizons; (2) separating the planning of products’ business goals from R&D resource allocation; (3) planning open-endedly with a pre-defined rhythm; (4) emphasizing whole-product thinking; and (5) making solution planning visible. To support whole-product thinking and solution planning, we suggest that companies create solution concepts. The purpose of the solution concept is to provide a big picture of the solution and guide RE activities.

[1]  Casper Lassenius,et al.  An Approach to Product Roadmapping in Small Software Product Businesses , 2002 .

[2]  D. Probert,et al.  Starting-up roadmapping fast , 2003, IEEE Engineering Management Review.

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

[4]  Steve Sawyer,et al.  Packaged software development teams: what makes them different? , 1998, Inf. Technol. People.

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

[6]  Mika V. Mäntylä,et al.  Pacing Software Product Development: A Framework and Practical Implementation Guidelines , 2004 .

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

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

[9]  Pete Sawyer,et al.  Packaged Software: Challenges for RE , 2000 .

[10]  Satish Nambisan,et al.  Why Service Businesses Are Not Product Businesses , 2001 .

[11]  James C. Spohrer,et al.  A research manifesto for services science , 2006, CACM.

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

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

[14]  Rita Gunther McGrath,et al.  Discovering new points of differentiation. , 1997, Harvard business review.

[15]  Christof Ebert,et al.  Requirements before the requirements: understanding the upstream impacts , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[16]  Barry W. Boehm.  Value-based software engineering: reinventing , 2003, SOEN.

[17]  Michael A. Cusumano,et al.  The Changing Software Business: Moving from Products to Services , 2008, Computer.

[18]  Jarno Vähäniitty,et al.  A tentative framework for connecting long-term business and product planning with iterative & incremental software product development , 2005, ACM SIGSOFT Softw. Eng. Notes.

[19]  Thomas A. Kappel,et al.  Perspectives on roadmaps: how organizations talk about the future , 2001 .

[20]  C. Grönroos.  Service Management and Marketing: Customer Management in Service Competition , 2007 .

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

[22]  Anthony F. Hutchings,et al.  Creating products customers demand , 1995, CACM.

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

[24]  Marjo Kauppinen,et al.  Strengthening the link between business decisions and RE: Long-term product planning in software product companies , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

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

[26]  Renée Mauborgne,et al.  Blue ocean strategy. , 2004, Harvard business review.

[27]  David Probert,et al.  Characterisation of technology roadmaps: purpose and format , 2001, PICMET '01. Portland International Conference on Management of Engineering and Technology. Proceedings Vol.1: Book of Summaries (IEEE Cat. No.01CH37199).

[28]  M. Patton.  Qualitative research and evaluation methods , 1980 .

[29]  K. Hambridge.  Action research. , 2000, Professional nurse.

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

[31]  Mark T True,et al.  Software Requirements , 2005 .

[32]  Claes Wohlin,et al.  Identification of key factors in software process management - a case study , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[33]  Marjo Kauppinen,et al.  Introducing requirements engineering: how to make a cultural change happen in practice , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[34]  Detlev J. Hoch,et al.  Secrets of Software Success: Management Insights from 100 Software Firms Around the World , 1999 .

[35]  K. Narasimhan,et al.  Service Management and Marketing: Customer Management in Service Competition (3rd ed.) , 2009 .

[36]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

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

[38]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[39]  Robert Phaal,et al.  Technology Roadmapping: Starting-Up Roadmapping Fast , 2003 .