Hall, T.

Jagielska, D.

Rainer, A.

English

University of Hertfordshire Research Archive

A framework for identifying software project risks,

A life span approach to cardiovascular disease risk and aging: The Fels Longitudinal Study.

A review of software surveys on software effort estimation,

After the appraisal: A systematic survey of process improvement”

An Empirical Investigation of Software Schedule Behaviour, Doctoral thesis. Depart of Computing,

An Experiment To Assess The Cost-Benefits Of Code Inspections In Large Scale Software Development,.

Assessing Test-driven Development at

Business Applications of Repertory Grid,

Content Analysis – An Introduction to Its Methodology. Sage Publications. Krueger RA and Casey MA, Focus Groups: A Practical Guide For Applied Research. Sage,

Evidence Based Software Engineering for Practitioners,

Inside the software design team: knowledge acquisition, sharing and integration.

Interaction Design,

Issues in using students in empirical studies

Key success factors for implementing software process improvement: a maturity-based analysis

Life Course Research. Development of a Field.

Mass imprisonment and the Life Course: Race and Class Inequality, Incarceration.

Motivators of Software Process Improvement: An Analysis of Practitioners' Views&quot;

Practitioner roles in Software Process Improvement: An analysis using

Preliminary guidelines for empirical research in software engineering,

Qualitative Methods in Empirical Studies of Soft Eng,

Researching Social Life,

Social Research,

Software engineering projects: How to evaluate success?,

Specific determinants of intrinsic work motivation, emotional exhaustion and turnover intention: A multisample longitudinal study.

The Research Act: a theoretical introduction to sociological methods,

Towards conceptual Framework for Mixed Method Evaluation Designs, Education Evaluation and Policy Analysis,

When To Use Focus Groups And Why, in Successful Focus Groups: Advancing The State Of The Art (Morgan DL ed), Sage,

Using software development progress data to understand threats to project outcomes

In this paper we describe our on-going longitudinal study of a large complex software development project. We discuss how we used project metrics data collected by the development team to identify threats to project outcomes. Identifying and addressing threats to projects early in the development process should significantly reduce the chances of project failure. We have analysed project data to pinpoint the sources of threats to the project. The data we have used is embedded in the project’s fortnightly progress reports produced by the project team. The progress reports are part of the software measurement program this company operates. The company has highly mature development processes which were assessed at CMM level 5 in 2004. Our analysis shows that standard project progress data can generate rich insights into the project; insights that go beyond those anticipated when the metrics were originally specified. Our results reveal a pattern of threats to the project that the project team can focus on mitigating. The project team is already aware of some threats, for example that communication with the customer is a significant threat to the project. But there are other threats the team is not aware of, for example that people issues within the software team are not a significant threat to the project. 

Tracy Hall

Austen Rainer

Dorota Jagielska

CiteSeerX

http://uhra.herts.ac.uk/bitstream/handle/2299/2079/902203.pdf;jsessionid=60F55E1B4446DB6A344ADF47BBB6C024?sequence=1

Using software development progress data to understand threats to project outcomes

Abstract

Similar works

Full text

Available Versions

University of Hertfordshire Research Archive

CiteSeerX