Benefits management in software development: A systematic review of empirical studies

Abstract Considerable resources are wasted on software projects delivering less than the planned benefits. Herein, the objective is to synthesize empirical evidence of the adoption and impact of benefits management (BM) in software development, and to suggest directions for future research. A system...

Full description

Bibliographic Details
Main Authors: Knut Kjetil Holgeid, Magne Jørgensen, Dag I. K. Sjøberg, John Krogstie
Format: Article
Language:English
Published: Wiley 2021-02-01
Series:IET Software
Online Access:https://doi.org/10.1049/sfw2.12007
id doaj-29a436c7441b494093184cfb2f02a83d
record_format Article
spelling doaj-29a436c7441b494093184cfb2f02a83d2021-08-02T08:25:07ZengWileyIET Software1751-88061751-88142021-02-0115112410.1049/sfw2.12007Benefits management in software development: A systematic review of empirical studiesKnut Kjetil Holgeid0Magne Jørgensen1Dag I. K. Sjøberg2John Krogstie3Department of Informatics University of Oslo Oslo NorwaySimula Metropolitan Center for Digital Engineering Lysaker NorwayDepartment of Informatics University of Oslo Oslo NorwayDepartment of Computer and Information Science NTNU Norwegian University of Science and Technology Trondheim NorwayAbstract Considerable resources are wasted on software projects delivering less than the planned benefits. Herein, the objective is to synthesize empirical evidence of the adoption and impact of benefits management (BM) in software development, and to suggest directions for future research. A systematic review of the literature is performed and identified 4836 scientific papers of which the authors found 47 to include relevant research. While most organizations identify and structure benefits at the outset of a project, fewer organizations report implementing BM as a continuous process throughout the project lifecycle. Empirical evidence gives support for positive impact on project outcome from the following BM practices: identifying and structuring benefits, planning benefits realization, BM during project execution, benefits evaluation and the practice of having people responsible for benefits realization. The authors suggest four research directions to understand (1) why BM practices sometimes not are adopted, (2) BM in relation to other management practices, (3) BM in agile software development and (4) BM in the context of organizations' value creation logics.https://doi.org/10.1049/sfw2.12007
collection DOAJ
language English
format Article
sources DOAJ
author Knut Kjetil Holgeid
Magne Jørgensen
Dag I. K. Sjøberg
John Krogstie
spellingShingle Knut Kjetil Holgeid
Magne Jørgensen
Dag I. K. Sjøberg
John Krogstie
Benefits management in software development: A systematic review of empirical studies
IET Software
author_facet Knut Kjetil Holgeid
Magne Jørgensen
Dag I. K. Sjøberg
John Krogstie
author_sort Knut Kjetil Holgeid
title Benefits management in software development: A systematic review of empirical studies
title_short Benefits management in software development: A systematic review of empirical studies
title_full Benefits management in software development: A systematic review of empirical studies
title_fullStr Benefits management in software development: A systematic review of empirical studies
title_full_unstemmed Benefits management in software development: A systematic review of empirical studies
title_sort benefits management in software development: a systematic review of empirical studies
publisher Wiley
series IET Software
issn 1751-8806
1751-8814
publishDate 2021-02-01
description Abstract Considerable resources are wasted on software projects delivering less than the planned benefits. Herein, the objective is to synthesize empirical evidence of the adoption and impact of benefits management (BM) in software development, and to suggest directions for future research. A systematic review of the literature is performed and identified 4836 scientific papers of which the authors found 47 to include relevant research. While most organizations identify and structure benefits at the outset of a project, fewer organizations report implementing BM as a continuous process throughout the project lifecycle. Empirical evidence gives support for positive impact on project outcome from the following BM practices: identifying and structuring benefits, planning benefits realization, BM during project execution, benefits evaluation and the practice of having people responsible for benefits realization. The authors suggest four research directions to understand (1) why BM practices sometimes not are adopted, (2) BM in relation to other management practices, (3) BM in agile software development and (4) BM in the context of organizations' value creation logics.
url https://doi.org/10.1049/sfw2.12007
work_keys_str_mv AT knutkjetilholgeid benefitsmanagementinsoftwaredevelopmentasystematicreviewofempiricalstudies
AT magnejørgensen benefitsmanagementinsoftwaredevelopmentasystematicreviewofempiricalstudies
AT dagiksjøberg benefitsmanagementinsoftwaredevelopmentasystematicreviewofempiricalstudies
AT johnkrogstie benefitsmanagementinsoftwaredevelopmentasystematicreviewofempiricalstudies
_version_ 1721238358347218944