Integrating Value and Utility Concepts into a Value Decomposition Model for Value-Based Software Engineering

Rönkkö, Mikko; Frühwirth, Christian; Biffl, Stefan

doi:10.1007/978-3-642-02152-7_27

Cited by 9 publications

(8 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several researchers have presented value constructs and corresponding valuation/measurement solutions needed for making decisions about software product development [9][10][11][12][13][14]. However, the contributions are often isolated and have a limited perspective, focusing on, for example, only cost, or only product characteristics like usability.…”

Section: The Absence Of a Consolidated View On Valuementioning

confidence: 99%

“…Value-based software engineering (VBSE) emphasizes that every decision and/or feature of a product does not have an equal value like in a value-neutral setting [2]. This requires making decisions that are better for overall value creation [8,9], and balancing shortterm and long-term value creation. To enable this, different perspectives and corresponding value constructs need to be considered together while making decisions for sustaining growth and maintaining the competitive advantage.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Khurum

Gorschek

Wilson

2012

J Software Evolu Process

101

View full text Add to dashboard Cite

SUMMARY In software intensive products such as cars or telecom systems, software has traditionally been associated with cost, and there has been no real perception of its value in relation to the entire product offering. However, because software is becoming a larger part of the main competitive advantage, driving innovation and product differentiation, hardware is becoming more standardized, thus the valuation of software is becoming critical. In existing literature, several value constructs and corresponding valuation/measurement solutions needed for making decisions about software product development are presented. However, the contributions are often isolated with respect to a certain perspective such as focusing on product's internal or external quality aspects only. Consequently, a complete view of value constructs relevant from different perspectives required for making decisions about software product development is missing. This paper presents a consolidated view of the software value concept utilizing the major perspectives and introduces a software value map. The created value map was evaluated through an industry case study through the development of impact evaluation patterns, which were subsequently used by professionals in industry, and experiences gathered. During industry evaluation, practitioners found substantial benefits of having a consolidated, vastly improved, and extended value aspect's view of software. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

Section: The Absence Of a Consolidated View On Valuementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Khurum

Gorschek

Wilson

2012

J Software Evolu Process

101

View full text Add to dashboard Cite

show abstract

“…Another approach that focuses on considering value during the software process is "Value-based Software Engineering" (VBSE) [7]. This approach provides di↵erent elements, such as techniques for determining value by analytical means, and methods for including value considerations into management activities [8,9]. Other related approaches exist, e.g.…”

Section: Related Workmentioning

confidence: 99%

Creating Minimum Viable Products in Industry-Academia Collaborations

Münch

Fagerholm

Johnson

et al. 2013

Lean Enterprise Software and Systems

View full text Add to dashboard Cite

Abstract. Customer value determines how products and services succeed in the marketplace. Early assessment of customer value is important for software startups, spin-o↵ companies, and new product development in existing companies. Software technology often influences customer value and typically defines the main competitive advantage in both entrepreneurial and intrapreneurial settings. Value-related feedback from real customers is needed during software development and maintenance, and decision-making should be increasingly based on empirical evidence acquired through experiments. Getting such value-related feedback usually requires a so-called minimum viable product (MVP), i.e., an artefact that may be incomplete in functionality or quality, but displays characteristics that allows determining its customer value. In this article we report on a case study which used industry-academia collaboration for creating such an MVP. Our goal was to identify strengths and weaknesses of such an approach to creating MVPs while providing practical recommendations for improvement. The process followed in the case study was found to be very suitable for creating MVPs, reducing company-specific risks when testing customer-value, and advancing university education.

show abstract

“…These authors identified the factors that determine the decisions about inclusion of certain requirements for implementation. Next, Rönkkö et al [18] present three aspects of software -as a technology, as a design, and as an artifact. They use these aspects to divide the value concept into three components that are relevant for software developing companies and their clients: intrinsic value, externalities and option value.…”

Section: Related Workmentioning

confidence: 99%

Business Value Is Not Only Dollars – Results from Case Study Research on Agile Software Projects

Racheva¹,

Daneva²,

Sikkel³

et al. 2010

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Business value is a key concept in agile software development. This paper presents results of a case study on how business value and its creation is perceived in the context of agile projects. Our overall conclusion is that the project participants almost never use an explicit and structured approach to guide the value creation throughout the project. Still, the application of agile methods in the studied cases leads to satisfied clients. An interesting result of the study represents the fact that the agile process of many projects differs significantly from what is described in the agile practitioners' books as best practices. The key implication for research and practice is that we have an incentive to pursue the study of value creation in agile projects and to complement it by providing guidelines for better client's involvement, as well as by developing structured methods that will enhance the value-creation in a project.

show abstract

Integrating Value and Utility Concepts into a Value Decomposition Model for Value-Based Software Engineering

Cited by 9 publications

References 44 publications

The software value map — an exhaustive collection of value aspects for the development of software intensive products

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Creating Minimum Viable Products in Industry-Academia Collaborations

Business Value Is Not Only Dollars – Results from Case Study Research on Agile Software Projects

Contact Info

Product

Resources

About