Standard

How to build a good practice software project portfolio? / Huijgens, Hennie; Van Solingen, Rini; Van Deursen, Arie.

36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings: Software Engineering In Practice Track (SEIP). Vol. 31-May-2014 IEEE Computer Society, 2014. p. 64-73.

Research output: Scientific - peer-reviewConference contribution

Harvard

Huijgens, H, Van Solingen, R & Van Deursen, A 2014, How to build a good practice software project portfolio? in 36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings: Software Engineering In Practice Track (SEIP). vol. 31-May-2014, IEEE Computer Society, pp. 64-73, 36th International Conference on Software Engineering, ICSE Companion 2014, Hyderabad, India, 31-7 June. DOI: 10.1145/2591062.2591187

APA

Huijgens, H., Van Solingen, R., & Van Deursen, A. (2014). How to build a good practice software project portfolio? In 36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings: Software Engineering In Practice Track (SEIP). (Vol. 31-May-2014, pp. 64-73). IEEE Computer Society. DOI: 10.1145/2591062.2591187

Vancouver

Huijgens H, Van Solingen R, Van Deursen A. How to build a good practice software project portfolio? In 36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings: Software Engineering In Practice Track (SEIP). Vol. 31-May-2014. IEEE Computer Society. 2014. p. 64-73. Available from, DOI: 10.1145/2591062.2591187

Author

Huijgens, Hennie; Van Solingen, Rini; Van Deursen, Arie / How to build a good practice software project portfolio?

36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings: Software Engineering In Practice Track (SEIP). Vol. 31-May-2014 IEEE Computer Society, 2014. p. 64-73.

Research output: Scientific - peer-reviewConference contribution

BibTeX

@inbook{99d2cb98733645efb3a07b2e5249e013,
title = "How to build a good practice software project portfolio?",
keywords = "Agile, Bad practice, Failure factor, Good practice, Learning cycle, Productivity, Quality, Success factor, Time-to-market",
author = "Hennie Huijgens and {Van Solingen}, Rini and {Van Deursen}, Arie",
year = "2014",
month = "5",
doi = "10.1145/2591062.2591187",
volume = "31-May-2014",
pages = "64--73",
booktitle = "36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings",
publisher = "IEEE Computer Society",
address = "United States",

}

RIS

TY - CHAP

T1 - How to build a good practice software project portfolio?

AU - Huijgens,Hennie

AU - Van Solingen,Rini

AU - Van Deursen,Arie

PY - 2014/5/31

Y1 - 2014/5/31

N2 - What can we learn from historic data that is collected in three software companies that on a daily basis had to cope with highly complex project portfolios? In this paper we analyze a large dataset, containing 352 finalized software engineering projects, with the goal to discover what factors affect software project performance, and what actions can be taken to increase project performance when building a software project portfolio. The software projects were classified in four quadrants of a Cost/Duration matrix: analysis was performed on factors that were strongly related to two of those quadrants, Good Practices and Bad Practices. A ranking was performed on the factors based on statistical significance. The paper results in an inventory of 'what factors should be embraced when building a project portfolio?' (Success Factors), and 'what factors should be avoided when doing so?' (Failure Factors). The major contribution of this paper is that it analyzes characteristics of best performers and worst performers in the dataset of software projects, resulting in 7 Success Factors (a.o. steady heartbeat, a fixed, experienced team, agile (Scrum), and release-based), and 9 Failure Factors (a.o. once-only project, dependencies with other systems, technology driven, and rules- and regulations driven).

AB - What can we learn from historic data that is collected in three software companies that on a daily basis had to cope with highly complex project portfolios? In this paper we analyze a large dataset, containing 352 finalized software engineering projects, with the goal to discover what factors affect software project performance, and what actions can be taken to increase project performance when building a software project portfolio. The software projects were classified in four quadrants of a Cost/Duration matrix: analysis was performed on factors that were strongly related to two of those quadrants, Good Practices and Bad Practices. A ranking was performed on the factors based on statistical significance. The paper results in an inventory of 'what factors should be embraced when building a project portfolio?' (Success Factors), and 'what factors should be avoided when doing so?' (Failure Factors). The major contribution of this paper is that it analyzes characteristics of best performers and worst performers in the dataset of software projects, resulting in 7 Success Factors (a.o. steady heartbeat, a fixed, experienced team, agile (Scrum), and release-based), and 9 Failure Factors (a.o. once-only project, dependencies with other systems, technology driven, and rules- and regulations driven).

KW - Agile

KW - Bad practice

KW - Failure factor

KW - Good practice

KW - Learning cycle

KW - Productivity

KW - Quality

KW - Success factor

KW - Time-to-market

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

U2 - 10.1145/2591062.2591187

DO - 10.1145/2591062.2591187

M3 - Conference contribution

VL - 31-May-2014

SP - 64

EP - 73

BT - 36th International Conference on Software Engineering, ICSE Companion 2014 - Proceedings

PB - IEEE Computer Society

ER -

ID: 7420252