Understanding software project risk: a cluster analysis

Understanding software project risk can help in reducing the incidence of failure. Building on prior work, software project risk was conceptualized along six dimensions. A questionnaire was built and 507 software project managers were surveyed. A cluster analysis was then performed to identify aspects of low, medium, and high risk projects. An examination of risk dimensions across the levels revealed that even low risk projects have a high level of complexity risk. For high risk projects, the risks associated with requirements, planning and control, and the organization become more obvious. The influence of project scope, sourcing practices, and strategic orientation on project risk dimensions was also examined. Results suggested that project scope affects all dimensions of risk, whereas sourcing practices and strategic orientation had a more limited impact. A conceptual model of project risk and performance was presented.

[1]  T. Moynihan,et al.  How Experienced Project Managers Assess Risk , 1997, IEEE Softw..

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

[3]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[4]  Linda Wallace.  The Development of an Instrument toMeasure Software Project Risk , 1997 .

[5]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[6]  H. Raghav Rao,et al.  Information systems outsourcing , 1996, CACM.

[7]  Blake Ives,et al.  User Involvement and MIS Success: A Review of Research , 1984 .

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

[9]  Ram L. Kumar,et al.  Managing risks in IT projects: an options perspective , 2002, Inf. Manag..

[10]  Karl G. Jöreskog,et al.  LISREL 7: A guide to the program and applications , 1988 .

[11]  Brad Tuttle,et al.  A Study of Staff Turnover, Acquisition, and Assimilation and Their Impact on Software Development Cost and Schedule , 1989, J. Manag. Inf. Syst..

[12]  Iris Vessey,et al.  The Effect of User Involvement on System Success: A Contingency Approach , 1988, MIS Q..

[13]  Jr. Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

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

[15]  Rudy Hirschheim,et al.  The myths and realities of information technology insourcing , 2000, CACM.

[16]  James Bret Michael,et al.  Quality management metrics for software development , 2003, Inf. Manag..

[17]  Peter A. Todd,et al.  Understanding Information Technology Usage: A Test of Competing Models , 1995, Inf. Syst. Res..

[18]  Blake Ives,et al.  Executive Involvement and Participation in the Management of Information Technology , 1991, MIS Q..

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

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

[21]  K. Eisenhardt.  Agency Theory: An Assessment and Review , 1989 .

[22]  M. J. Earl,et al.  The Risks of Outsourcing IT , 1996 .

[23]  F. Warren McFarlan,et al.  Corporate information systems management : text and cases , 1988 .

[24]  J. March,et al.  Managerial perspectives on risk and risk taking , 1987 .

[25]  Robert W. Zmud,et al.  Management of Large Software Development Efforts , 1980, MIS Q..

[26]  Gary Klein,et al.  Project Risk Impact on Software Development Team Performance , 2000 .

[27]  Michael S. Deutsch,et al.  An exploratory analysis relating the software project management process to project success , 1991 .

[28]  Richard H. Thayer,et al.  Special Feature The Challenge of Software Engineering Project Management , 1980, Computer.

[29]  Capers Jones,et al.  Assessment and control of software risks , 1994, Yourdon Press Computing Series.

[30]  Gary Klein,et al.  Risks to different aspects of system success , 1999, Inf. Manag..

[31]  Robert N. Charette,et al.  Software Engineering Risk Analysis and Management , 1989 .

[32]  Sarma R. Nidumolu.  The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable , 1995, Inf. Syst. Res..

[33]  Arun Rai,et al.  The effects of development process modeling and task uncertainty on development quality performance , 2000, Inf. Manag..

[34]  Ralph L. Kliem,et al.  Managing the Risks of Outsourcing Agreements , 1999, Inf. Syst. Manag..

[35]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[36]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[37]  Timo Saarinen,et al.  System development methodology and project success: An assessment of situational approaches , 1990, Inf. Manag..

[38]  Suzanne Rivard,et al.  Toward an Assessment of Software Development Risk , 1993, J. Manag. Inf. Syst..

[39]  Philip W. Metzger.  Managing a programming project , 1973 .

[40]  Laurie J. Kirsch,et al.  Portfolios of Control Modes and IS Project Management , 1997, Inf. Syst. Res..

[41]  Stephen Ward.  Requirements for an Effective Project Risk Management Process , 1999 .

[42]  Kenneth R. MacCrimmon,et al.  The Risk In-Basket , 1984 .

[43]  David McComb,et al.  System project failure : the heuristics of risk , 1991 .

[44]  Eric K. Clemons,et al.  Evaluation of strategic investments in information technology , 1991, CACM.

[45]  Daniel Robey,et al.  User Involvement in Information System Development: A Conflict Model and Empirical Test , 1982 .

[46]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[47]  Sarma R. Nidumolu.  A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination in Software Development Projects , 1996, J. Manag. Inf. Syst..

[48]  Jeffrey H. Moore,et al.  A Framework for MIS Software Development Projects , 1979, MIS Q..

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

[50]  Stephen P. Keider,et al.  Why Systems Development Projects Fail , 1984 .

[51]  Don Tapscott,et al.  Digital capital: harnessing the power of business Webs , 2000, UBIQ.

[52]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[53]  M. C. Jensen,et al.  Harvard Business School; SSRN; National Bureau of Economic Research (NBER); European Corporate Governance Institute (ECGI); Harvard University - Accounting & Control Unit , 1976 .

[54]  John H Lehman,et al.  Software Engineering Project Management: A Survey Concerning U. S. Aerospace Industry Management of Software Development Projects. , 1977 .

[55]  Z. G. Ruthberg,et al.  Work priority scheme for EDP audit and computer security review , 1989 .

[56]  John J. Sviokla,et al.  Managing in the Marketspace , 1994 .