Standard

The effects of perceived value and stakeholder satisfaction on software project impact. / Huijgens, Hennie; van Deursen, Arie; van Solingen, Rini.

In: Information and Software Technology, Vol. 89, No. September, 09.2017, p. 19-36.

Research output: Scientific - peer-reviewArticle

Harvard

APA

Vancouver

Author

Huijgens, Hennie; van Deursen, Arie; van Solingen, Rini / The effects of perceived value and stakeholder satisfaction on software project impact.

In: Information and Software Technology, Vol. 89, No. September, 09.2017, p. 19-36.

Research output: Scientific - peer-reviewArticle

BibTeX

@article{41369284f0ea4057adf326826893cf85,
title = "The effects of perceived value and stakeholder satisfaction on software project impact",
keywords = "Cost duration index, Evidence-based software engineering, Perceived value, Software economics, Stakeholder satisfaction",
author = "Hennie Huijgens and {van Deursen}, Arie and {van Solingen}, Rini",
year = "2017",
month = "9",
doi = "10.1016/j.infsof.2017.04.008",
volume = "89",
pages = "19--36",
journal = "Information and Software Technology",
issn = "0950-5849",
publisher = "Elsevier",
number = "September",

}

RIS

TY - JOUR

T1 - The effects of perceived value and stakeholder satisfaction on software project impact

AU - Huijgens,Hennie

AU - van Deursen,Arie

AU - van Solingen,Rini

PY - 2017/9

Y1 - 2017/9

N2 - Context: In this paper we present a multiple case study on the insights of software organizations into stakeholder satisfaction and (perceived) value of their software projects. Our study is based on the notion that quantifying and qualifying project size, cost, duration, defects, and estimation accuracy needs to be done in relation with stakeholder satisfaction and perceived value. Objectives: We contrast project metrics such as cost, duration, number of defects and estimation accuracy with stakeholder satisfaction and perceived value. Method: In order to find out whether our approach is practically feasible in an industrial setting, we performed two case studies; one in a Belgian telecom company and the other in a Dutch software company. Results: In this study we evaluate 22 software projects that were delivered during one release in the Belgian telecom company, and 4 additional large software releases (representing an extension of 174% in project size) that were delivered in a Dutch software company. Eighty-three (83) key stakeholders of two companies provide stakeholder satisfaction and perceived value measurements in 133 completed surveys. Conclusions: We conclude that a focus on shortening overall project duration, and improving communication and team collaboration on intermediate progress is likely to have a positive impact on stakeholder satisfaction and perceived value. Our study does not provide any evidence that steering on costs helped to improve these. As an answer to our research question - how do stakeholder satisfaction and perceived value relate to cost, duration, defects, size and estimation accuracy of software projects? - we found five take-away-messages.

AB - Context: In this paper we present a multiple case study on the insights of software organizations into stakeholder satisfaction and (perceived) value of their software projects. Our study is based on the notion that quantifying and qualifying project size, cost, duration, defects, and estimation accuracy needs to be done in relation with stakeholder satisfaction and perceived value. Objectives: We contrast project metrics such as cost, duration, number of defects and estimation accuracy with stakeholder satisfaction and perceived value. Method: In order to find out whether our approach is practically feasible in an industrial setting, we performed two case studies; one in a Belgian telecom company and the other in a Dutch software company. Results: In this study we evaluate 22 software projects that were delivered during one release in the Belgian telecom company, and 4 additional large software releases (representing an extension of 174% in project size) that were delivered in a Dutch software company. Eighty-three (83) key stakeholders of two companies provide stakeholder satisfaction and perceived value measurements in 133 completed surveys. Conclusions: We conclude that a focus on shortening overall project duration, and improving communication and team collaboration on intermediate progress is likely to have a positive impact on stakeholder satisfaction and perceived value. Our study does not provide any evidence that steering on costs helped to improve these. As an answer to our research question - how do stakeholder satisfaction and perceived value relate to cost, duration, defects, size and estimation accuracy of software projects? - we found five take-away-messages.

KW - Cost duration index

KW - Evidence-based software engineering

KW - Perceived value

KW - Software economics

KW - Stakeholder satisfaction

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

U2 - 10.1016/j.infsof.2017.04.008

DO - 10.1016/j.infsof.2017.04.008

M3 - Article

VL - 89

SP - 19

EP - 36

JO - Information and Software Technology

T2 - Information and Software Technology

JF - Information and Software Technology

SN - 0950-5849

IS - September

ER -

ID: 19482628