Making Sense of Product Requirements

This paper takes a historical perspective to more than 40 years of software development within a company that is delivering its products to a diverse set of customers throughout the world. By examining the company’s past, we wish to find origins and potential remedies for the challenges that many companies presently face in determining just which, of many, features shall be implemented to forthcoming versions of their software products. We have concluded that the product-related design problems that once were manageable with rational thinking have gradually evolved into problems that have multiple and conflicting interpretations, different value orientations, unclear goals, contradictions and paradoxes. These problems occur due to the demands imposed by larger and much more diverse sets of critical stakeholders drawn from the new global business environment with its multi-cultural needs and greater numbers of highly domain-skilled, computer naïve users. For such problems sense making rather than decision making has begun to be the central organizational issue.

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

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

[3]  Björn Regnell,et al.  An industrial survey of requirements interdependencies in software product release planning , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[4]  Ian Sommerville,et al.  Improving Market-Driven RE Processes , 1999 .

[5]  Colin Potts,et al.  Invented requirements and imagined customers: requirements engineering for off-the-shelf software , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

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

[7]  M. McCaskey.  The Executive Challenge: Managing Change and Ambiguity , 1982 .

[8]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[9]  A Etzioni,et al.  Humble decision making. , 1989, Harvard business review.

[10]  Erran Carmel,et al.  Customer-developer links in software development , 1995, CACM.

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

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

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

[14]  Guy Fitzgerald,et al.  Where now for development methodologies? , 2003, CACM.

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

[16]  Steve Sawyer,et al.  A market-based perspective on information systems development , 2001, CACM.

[17]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

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

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

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

[21]  Steven Sawyer,et al.  Packaged software: implications of the differences from custom approaches to software development , 2000, Eur. J. Inf. Syst..

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

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