Key stakeholder's value propositions for feature selection in software-intensive products

an industrial case study

Pilar Rodriguez, Emilia Mendes, Burak Turhan

Research output: Contribution to journalArticleResearchpeer-review

Abstract

Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders’ value propositions when selecting features for a large telecommunications company’s software-intensive product. Stakeholders’ value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.

Original languageEnglish
Number of pages24
JournalIEEE Transactions on Software Engineering
DOIs
Publication statusAccepted/In press - 2019

Keywords

  • Case Study
  • Decision-making
  • Feature Selection
  • Grounded Theory
  • Key Stakeholders
  • Release Planning
  • Software-intensive Systems
  • Stakeholder Analysis
  • Value Proposition
  • Value-based Software Engineering (VBSE)

Cite this

@article{ee296f8e695447c1a9e48ad7a07a49a9,
title = "Key stakeholder's value propositions for feature selection in software-intensive products: an industrial case study",
abstract = "Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders’ value propositions when selecting features for a large telecommunications company’s software-intensive product. Stakeholders’ value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.",
keywords = "Case Study, Decision-making, Feature Selection, Grounded Theory, Key Stakeholders, Release Planning, Software-intensive Systems, Stakeholder Analysis, Value Proposition, Value-based Software Engineering (VBSE)",
author = "Pilar Rodriguez and Emilia Mendes and Burak Turhan",
year = "2019",
doi = "10.1109/TSE.2018.2878031",
language = "English",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Publ by IEEE",

}

Key stakeholder's value propositions for feature selection in software-intensive products : an industrial case study. / Rodriguez, Pilar; Mendes, Emilia; Turhan, Burak.

In: IEEE Transactions on Software Engineering, 2019.

Research output: Contribution to journalArticleResearchpeer-review

TY - JOUR

T1 - Key stakeholder's value propositions for feature selection in software-intensive products

T2 - an industrial case study

AU - Rodriguez, Pilar

AU - Mendes, Emilia

AU - Turhan, Burak

PY - 2019

Y1 - 2019

N2 - Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders’ value propositions when selecting features for a large telecommunications company’s software-intensive product. Stakeholders’ value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.

AB - Numerous software companies are adopting value-based decision making. However, what does value mean for key stakeholders making decisions? How do different stakeholder groups understand value? Without an explicit understanding of what value means, decisions are subject to ambiguity and vagueness, which are likely to bias them. This case study provides an in-depth analysis of key stakeholders’ value propositions when selecting features for a large telecommunications company’s software-intensive product. Stakeholders’ value propositions were elicited via interviews, which were analyzed using Grounded Theory coding techniques (open and selective coding). Thirty-six value propositions were identified and classified into six dimensions: customer value, market competitiveness, economic value/profitability, cost efficiency, technology & architecture, and company strategy. Our results show that although propositions in the customer value dimension were those mentioned the most, the concept of value for feature selection encompasses a wide range of value propositions. Moreover, stakeholder groups focused on different and complementary value dimensions, calling to the importance of involving all key stakeholders in the decision making process. Although our results are particularly relevant to companies similar to the one described herein, they aim to generate a learning process on value-based feature selection for practitioners and researchers in general.

KW - Case Study

KW - Decision-making

KW - Feature Selection

KW - Grounded Theory

KW - Key Stakeholders

KW - Release Planning

KW - Software-intensive Systems

KW - Stakeholder Analysis

KW - Value Proposition

KW - Value-based Software Engineering (VBSE)

UR - http://www.scopus.com/inward/record.url?scp=85055718719&partnerID=8YFLogxK

U2 - 10.1109/TSE.2018.2878031

DO - 10.1109/TSE.2018.2878031

M3 - Article

JO - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

ER -