ACM Home Page
Please provide us with feedback. Feedback
The impact of staff turnover on software projects: the importance of understanding what makes software practitioners tick
Full text PdfPdf (286 KB)
Source
Special Interest Group on Computer Personnel Research Annual Conference archive
Proceedings of the 2008 ACM SIGMIS CPR conference on Computer personnel doctoral consortium and research table of contents
Charlottesville, VA, USA
SESSION: Software table of contents
Pages 30-39  
Year of Publication: 2008
ISBN:978-1-60558-069-2
Authors
Tracy Hall  Brunel University, Middlesex, United Kingdom
Sarah Beecham  University of Hertfordshire, Hatfield, United Kingdom
June Verner  National ICT Australia, Sydney, Australia
David Wilson  University of Technology, Sydney, Sydney, Australia
Sponsors
SIGMIS: ACM Special Interest Group on Management Information Systems
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 22,   Downloads (12 Months): 158,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1355238.1355245
What is a DOI?

ABSTRACT

In this paper we investigate the impact of staff turnover on software projects. In particular we investigate whether high staff turnover damages project success. We analyse data from an empirical study of 89 software practitioners to show that projects with high staff turnover are less successful. Furthermore our empirical data suggests a relationship between high staff turnover on projects and low staff motivation levels. We discuss factors which have been previously found to improve motivation levels and conclude that improving motivation levels can reduce staff turnover, which in turn increases project success.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
3
 
4
Bennatan, E. M., On Time Within Budget, John Wiley and Sons, 2000.
 
5
 
6
 
7
Bourzac, K. The Trouble with Software. Technology Review, 2007, 110(1): p. 88
 
8
 
9
Charettte, R., Why software fails, IEEE Spectrum, September, 2005, pp.42--49.
10
 
11
 
12
Frangos, S. A., Motivated humans for reliable software products. Microprocessors and Microsystems, 1997. 21(10): p. 605--610.
13
 
14
Glass, R. L,. Software Runaways, Prentice-Hall, New York, 1998.
 
15
Glass R. L., Facts and Fallacies of Software Engineering, Addison Wesley, 2002.
 
16
IDS, Improving staff retention, IDS HR Studies, IDS Study 765, January 2004.
 
17
Jørgensen, M. and Moløkken-Østvold, K. How large are software cost overruns? A review of the 1994 CHAOS report, Information and Software Technology, 48, 2006, pp. 297--301.
 
18
Langley, N., Software Tests may be Automated but the Human Element is Crucial, Computer Weekly, 22nd November 2005
 
19
 
20
Latimer, D., The Cost of IT Staff Turnover: A Quantitative Approach, EDUCAUSE Center for Applied Research,Research Bulletin Volume 2002, Issue 4, 19th February 2002.
21
 
22
 
23
 
24
 
25
 
26
Poulsen, K. Software Bug Contributed to Blackout, Security Focus. 11th February 2004
 
27
28
29
 
30
Pinto, J. K. and Mandel, S. J., The Causes of Project Failure, IEEE Transactions on Engineering Management, 34, 7, November, 1990.
 
31
 
32
 
33
Rubenstein, D., Standish Group Report: There's Less Development Chaos Today, SD Times, 1st March 2007, Accessed 2nd November 2007 http://www.sdtimes.com/article/story-20070301-01.html
 
34


Collaborative Colleagues:
Tracy Hall: colleagues
Sarah Beecham: colleagues
June Verner: colleagues
David Wilson: colleagues