Controlling software project risks: an empirical study of methods used by experienced project managers

The failure rate of software projects has been proven to be very high, and the incidence of failure is becoming worse as more companies venture into software development. Risk management is a collection of methods aimed at minimising or reducing the effects of project failure. This research report has focused on experienced project manager's perceptions of software project risks and controls. It reports on the more significant risks and controls that are utilised to reduce the occurrence of the risk factors, or minimise the impact of various risks. Risk factors involved in software projects along with controls to mitigate these factors were identified in the literature. These were then used in an empirical study to determine their importance and frequency of occurrence. The effectiveness of various controls to reduce the occurrence of risk factors was also identified and discussed. Experienced project managers were found to use certain controls more than inexperienced project managers, particularly 'assign responsibilities to team members' and 'stabilise requirements and specifications'.

[1]  Kalle Lyytinen,et al.  Strategies for Heading Off is Project Failure , 2000, Inf. Syst. Manag..

[2]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[3]  Kishore Sengupta,et al.  The Impact of Goals On Software Project Management: An Experimental Investigation , 1999, MIS Q..

[4]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.

[5]  J Ropponen,et al.  Can software risk management improve system development: an exploratory study , 1997 .

[6]  Daniel W. Robert Creating an Environment for Project Success , 1997, Inf. Syst. Manag..

[7]  Thomas W. Lauer,et al.  Software project managers' risk preferences , 1996, J. Inf. Technol..

[8]  Robert Phelps,et al.  Risk management and agency theory in IS projects — an exploratory study , 1996, J. Inf. Technol..

[9]  Jonathan H. Klein,et al.  Risk management for information systems development , 1996, J. Inf. Technol..

[10]  Rob J. Kusters,et al.  Dealing with risk: a practical approach , 1996, J. Inf. Technol..

[11]  F. McFarlan,et al.  Corporate Information Systems Management: Issues Facing Senior Executives , 1995 .

[12]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[13]  Carol V. Brown,et al.  Managing Information Technology: What Managers Need to Know , 1994 .

[14]  Kishore Sengupta,et al.  Software Project Control: An Experimental Investigation of Judgment with Fallible Information , 1993, IEEE Trans. Software Eng..

[15]  Frank E. McGarry,et al.  Recommended approach to software development, revision 3 , 1992 .

[16]  Zbigniew H. Przasnyski,et al.  On Information Systems Project Abandonment: An Exploratory Study of Organizational Practices , 1991, MIS Q..

[17]  B. Boehm Software risk management: principles and practices , 1991, IEEE Software.

[18]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[19]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

[20]  John C. Anderson,et al.  Assessing Project Implementation Risk: A Methodological Approach , 1979 .

[21]  Earl R. Babbie,et al.  The practice of social research , 1969 .