Decision Support for Product Management of Software Intensive Products

Context: At the core of choosing what features and level of quality to realize, and thus offer a market or customer, rests on the ability to take decisions. Decision-making is complicated by the diverse understanding of issues such as priority, consequence of realization, and interpretations of strategy as pertaining to the short-term and long-term development of software intensive products. The complexity is further compounded by the amount of decision support material that has to be taken into account, and the sheer volume of possible alternatives that have to be triaged and prioritized; thousands or even tens of thousands of requirements can be the reality facing a company. There is a need to develop the functionality that is strategically most significant, while satisfying customers and being competitive, time efficient, cost effective, and risk minimizing. In order to achieve a balance between these factors, all the stakeholders, within an organization, need to agree on the strategic aspects and value considerations to be considered, and their corresponding relative importance. Objective: The objective of this thesis is to provide enhanced decision support for product managers faced with decision-making challenges. This involves, but is not limited to, enhancing the alignment between the product and portfolio management with respect to product strategies, and enabling the use of value as a basis for product management and development related decisions. Method: A number of empirical studies, set in industry, have been performed. The research methods used span from systematic mapping, and systematic reviews to case studies, all aligned to identify possibilities for improvement, devise solutions, and incrementally evaluate said solutions. Close collaboration with industry partners was at the core of the research presented in this thesis. Result: The MASS method presented in this thesis can be used to evaluate strategic alignment and identify possible root causes for misalignment. To strengthen strategic alignment, the Software Value Map and corresponding decision support material, proposed in the thesis, can be used by product managers for making effective and efficient strategic decisions in relation to portfolios, products and process improvement, following a systematic and aligned process. Conclusions: The area of software product management, in the context of market-driven software intensive product development, is a field with unique challenges. The specifics of the solutions are based on industry case studies performed to gauge state-of-the-art, as well as identify the main challenges. The decision support developed takes the form of maps and frameworks that support software product management on product and portfolio level decisions, strategic alignment, value-based requirements selection, and value-based process improvement.

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

[2]  Yolande E. Chan,et al.  Assessing realized information systems strategy , 1997, J. Strateg. Inf. Syst..

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

[4]  Steven B. Dolins Using the balanced scorecard process to compute the value of software applications , 2006, ICSE '06.

[5]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

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

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

[8]  Raymond Papp,et al.  STRATEGIC ALIGNMENT: ANALYSIS OF PERSPECTIVES , 2006 .

[9]  John C. Henderson,et al.  Strategic alignment: a model for organizational transformation via information technology , 2011 .

[10]  Erik Simmons,et al.  Requirements Triage: What Can We Learn from a "Medical" Approach? , 2004, IEEE Softw..

[11]  R. Dorf,et al.  The Balanced Scorecard: Translating Strategy Into Action , 1997, Proceedings of the IEEE.

[12]  Claes Wohlin,et al.  A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts , 2007, REFSQ.

[13]  Claudio U. Ciborra,et al.  De profundis? Deconstructing the concept of strategic alignment , 1997, Scand. J. Inf. Syst..

[14]  Paul B. Cragg,et al.  Measuring strategic alignment in small firms , 1996, Proceedings of 1996 Information Systems Conference of New Zealand.

[15]  M. Porter What is strategy , 2000 .

[16]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..

[17]  Izak Benbasat,et al.  Factors That Influence the Social Dimension of Alignment Between Business and Information Technology Objectives , 2000, MIS Q..

[18]  J. Liebowitz,et al.  Developing knowledge management metrics for measuring intellectual capital , 2000 .

[19]  Alan M. Davis,et al.  The Art of Requirements Triage , 2003, Computer.

[20]  T. Greenhalgh,et al.  Effectiveness and efficiency of search methods in systematic reviews of complex evidence: audit of primary sources , 2005, BMJ : British Medical Journal.

[21]  Patrik Berander,et al.  Evolving Prioritization for Software Product Management , 2007 .

[22]  Prasad Chalasani,et al.  Software Design Decisions As Real Options , 1997 .

[23]  Jerry N. Luftman Assessing Business-IT Alignment Maturity , 2000, Commun. Assoc. Inf. Syst..

[24]  Tony Gorschek,et al.  Industry evaluation of the Requirements Abstraction Model , 2007, Requirements Engineering.

[25]  Claes Wohlin,et al.  Aligning Requirements with Business Objectives : A Framework for Requirements Engineering Decisions , 2005 .

[26]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

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

[28]  Karl T. Ulrich,et al.  Special Issue on Design and Development: Product Development Decisions: A Review of the Literature , 2001, Manag. Sci..

[29]  J. Fleiss Measuring nominal scale agreement among many raters. , 1971 .

[30]  M. Mcgrath Product Strategy for High Technology Companies , 2000 .

[31]  David E. Avison,et al.  Using and validating the strategic alignment model , 2004, J. Strateg. Inf. Syst..

[32]  Tony Gorschek,et al.  A Method for Early Requirements Triage and Selection Utilizing Product Strategies , 2007, 14th Asia-Pacific Software Engineering Conference (APSEC'07).

[33]  Erran Carmel,et al.  A process model for packaged software development , 1995 .

[34]  Tony Gorschek,et al.  A practitioner's guide to light weight software process assessment and improvement planning , 2008, J. Syst. Softw..

[35]  Eduardo S. Schwartz,et al.  Investment Under Uncertainty. , 1994 .

[36]  James M. Utterback,et al.  Mastering the Dynamics of Innovation: How Companies Can Seize Opportunities in the Face of Technological Change , 1994 .

[37]  Alyssa S. Dver Software Product Management Essentials , 2003 .

[38]  Jerry N. Luftman Assessing It/Business Alignment , 2003, Inf. Syst. Manag..

[39]  Jerry N. Luftman,et al.  Enablers and Inhibitors of Business-IT Alignment , 1999, Commun. Assoc. Inf. Syst..

[40]  Bernard J. Jaworski,et al.  Market orientation: Antecedents and consequences , 1993 .

[41]  Barry Boehm,et al.  Software economics: a roadmap , 2000, ICSE '00.

[42]  Pearl Brereton,et al.  Lessons from applying the systematic literature review process within the software engineering domain , 2007, J. Syst. Softw..

[43]  O. Dieste,et al.  Developing Search Strategies for Detecting Relevant Experiments for Systematic Reviews , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[44]  Khaled El Emam,et al.  A field study of requirements engineering practices in information systems development , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[45]  Norman E. Fenton,et al.  Software Metrics: A Rigorous Approach , 1991 .

[46]  Tomasz Smaczny Is an alignment between business and information technology the appropriate paradigm to manage IT in today’s organisations? , 2001 .

[47]  Tony Gorschek,et al.  A controlled empirical evaluation of a requirements abstraction model , 2007, Inf. Softw. Technol..

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

[49]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[50]  R. Kaplan,et al.  The balanced scorecard--measures that drive performance. , 2015, Harvard business review.

[51]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.