Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
article

Understanding software project risk: a cluster analysis

Published: 01 December 2004 Publication History

Abstract

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.

References

[1]
{1} T.K. Abdel-Hamid, A study of staff turnover, acquisition, and assimilation and their impact on software development cost and schedule, Journal of Management Information Systems 6 (1), 1989, pp. 21-39.]]
[2]
{2} S. Alter, M. Ginzberg, Managing uncertainty in MIS implementation, Sloan Management Review 20 (1), 1978, pp. 23-31.]]
[3]
{3} L.M. Applegate, F.W. McFarlan, J.L. McKenney, Corporate Information Systems Management: Text and Cases, Irwin, Chicago, 1996.]]
[4]
{4} H. Barki, S. Rivard, J. Talbot, Toward an assessment of software development risk, Journal of Management Information Systems 10 (2), 1993, pp. 203-225.]]
[5]
{5} B.W. Boehm, Software risk management: principles and practices, IEEE Software 8 (1), 1991, pp. 32-41.]]
[6]
{6} F.P. Brooks, The Mythical Man-Month, Addison-Wesley, Reading, MA, 1975.]]
[7]
{7} F.P. Brooks, No silver bullet: essence and accidents of software engineering, Computer 22 (4), (April 1987) 10-19.]]
[8]
{8} R.N. Charette, Software Engineering Risk Analysis and Management, Intertext Publications, New York, 1989.]]
[9]
{9} E. Clemons, Evaluation of strategic investments in information technology, Communications of the ACM 34 (1), 1991, pp. 22-36.]]
[10]
{10} J. Cumming, IT portfolio management: balancing risks and rewards of projects yields significant returns, NetworkWorld 19 (13), 2002, pp. 48.]]
[11]
{11} B. Curtis, H. Krasner, N. Iscoe, Field study of the software design process for large systems, Communications of the ACM 31 (11), 1988, pp. 1268-1287.]]
[12]
{12} G.B. Davis, Strategies for information requirements determination, IBM Systems Journal 21 (1), 1982, pp. 4-30.]]
[13]
{13} M. Deutsch, An exploratory analysis relating the software project management process to project success, IEEE Transactions on Engineering Management 38 (4), 1991, pp. 365-375.]]
[14]
{14} M.J. Earl, The risks of outsourcing IT, Sloan Management Review 37 (3), (Spring 1996) 26-32.]]
[15]
{15} K.M. Eisenhardt, Agency theory: an assessment and review, Academy of Management Review 14 (1), 1989, pp. 57-74.]]
[16]
{16} K. Ewusi-Mensah, Z.H. Przasnyski, On information systems project abandonment: an exploratory study of organizational practices, MIS Quarterly 15 (1), 1991, pp. 67-85.]]
[17]
{17} F.J. Heemstra, R.J. Kusters, Dealing with risk: a practical approach, Journal of Information Technology 11 (4), 1996, pp. 333-346.]]
[18]
{18} R. Hirschheim, M. Lacity, The myths and realities of information technology insourcing, Communications of the ACM 43 (2), 2000, pp. 99-107.]]
[19]
{19} A.S. Horowitz, Extreme outsourcing: does it work?, Computerworld 33 (19), (May 1999) 50-51.]]
[20]
{20} B. Ives, M.H. Olson, User involvement and MIS success: a review of research, Management Science 30 (5), 1984, pp. 586-603.]]
[21]
{21} S.L. Jarvenpaa, B. Ives, Executive involvement and participation in the management of information technology, MIS Quarterly 15 (2), 1991, pp. 205-277.]]
[22]
{22} M.C. Jensen, W.H. Meckling, Theory of the firm: managerial behavior, agency costs and ownership structure, Journal of Financial Economics 3, 1976, pp. 305-360.]]
[23]
{23} J.J. Jiang, G. Klein, Risks to different aspects of system success, Information and Management 36, 1999, pp. 264-272.]]
[24]
{24} J.J. Jiang, G. Klein, T. Means, Project risk impact on software development team performance, Project Management Journal 31 (4), (December 2000) 19-26.]]
[25]
{25} C. Jones, Assessment and Control of Software Risks, Yourdon Press, Englewood Cliffs, NJ, 1994.]]
[26]
{26} M.M. Jones, E.R. McLean, Management problems in large-scale software development projects, Industrial Management Review 11 (3), 1970, pp. 1-15.]]
[27]
{27} K.G. Joreskog, D. Sorbom, LISREL 7: a guide to the program and applications, SPSS Inc., Chicago, 1989.]]
[28]
{28} S.P. Keider, Why systems development projects fail, Journal of Information Systems Management 1 (3), 1984, pp. 33-38.]]
[29]
{29} M. Keil, P. Cule, K. Lyytinen, R. Schmidt, A framework for identifying software project risks, Communications of the ACM 41 (11), 1998, pp. 76-83.]]
[30]
{30} C.F. Kemerer, G.L. Sosa, Systems development risks in strategic information systems, Information and Software Technology 33 (3), 1991, pp. 212-223.]]
[31]
{31} L. Kirsch, Portfolios of control modes and is project management, Information Systems Research 8 (3), 1997, pp. 215-239.]]
[32]
{32} R. Kliem, Managing the risks of outsourcing agreements, Information Systems Management 16 (3), 1999, pp. 91-93.]]
[33]
{33} R. Kumar, Managing risks in IT projects: an options perspective, Information and Management 40, 2002, pp. 63- 74.]]
[34]
{34} K. Lyytinen, R. Hirschheim, Information systems failures--a survey and classification of the empirical literature, Oxford Surveys in Information Technology 4, 1987, pp. 257-309.]]
[35]
{35} K.R. MacCrimmon, D.A. Wehrung, The risk in-basket, Journal of Business 57 (3), 1984, pp. 367-387.]]
[36]
{36} J.G. March, Z. Shapira, Managerial perspectives on risk and risk taking, Management Science 33 (11), 1987, pp. 1404-1418.]]
[37]
{37} D. McComb, J.Y. Smith, System project failure: the heuristics of risk, Journal of Information Systems Management 8 (1), 1991, pp. 25-34.]]
[38]
{38} F.W. McFarlan, Portfolio approach to information systems, Harvard Business Review 59 (5), 1981, pp. 142-150.]]
[39]
{39} P.W. Metzger, Managing a Programming Project, Prentice-Hall, Englewood Cliffs, NJ, 1981.]]
[40]
{40} J.H. Moore, A framework for MIS software development projects, MIS Quarterly 3 (1), 1979, pp. 29-38.]]
[41]
{41} T. Moynihan, How experienced project managers assess risk, IEEE Software 14 (3), 1997, pp. 35-41.]]
[42]
{42} S. Nidumolu, The effect of coordination and uncertainty on software project performance: residual performance risk as an intervening variable, Information Systems Research 6 (3), 1995, pp. 191-219.]]
[43]
{43} S.R. Nidumolu, A comparison of the structural contingency and risk-based perspectives on coordination in software-development projects, Journal of Management Information Systems 13 (2), 1996, pp. 77-113.]]
[44]
{44} J.C. Nunnally, I.H. Bernstein, Psychometric Theory, McGraw-Hill, New York, 1994.]]
[45]
{45} J.S. Osmundson, J.B. Michael, M.J. Machniak, M.A. Grossman, Quality management metrics for software development, Information and Management 40, 2003, pp. 799-812.]]
[46]
{46} R.J.W. O'Toole, E.F. O'Toole, Top executive involvement in the EDP function, PMM & Co-Management Controls (June 1966) 125-127.]]
[47]
{47} A. Rai, H. Al-Hindi, The effects of development process modeling and task uncertainty on development quality performance, Information and Management 37, 2000, pp. 335-346.]]
[48]
{48} H.R. Rao, K. Nam, A. Chaudhury, Information systems outsourcing, Communications of the ACM 39 (7), 1996, pp. 27-28.]]
[49]
{49} J.F. Rayport, J.J. Sviokla, Managing in the marketspace, Harvard Business Review 72, 1994, pp. 141-150.]]
[50]
{50} D. Robey, D.L. Farrow, User involvement in information systems development: a conflict model and empirical test, Management Science 28 (1), 1982, pp. 73-85.]]
[51]
{51} J. Ropponen, K. Lyytinen, Can software risk management improve systems development: an exploratory study, European Journal of Information Systems 6 (6), 1996, pp. 41-50.]]
[52]
{52} Z.G. Ruthberg, B.T. Fisher, Work priority scheme for EDP audit and computer security review, National Bureau of Standards Technical Report, NBSIR 86-3386, March 1986, p. iii-B-14.]]
[53]
{53} T. Saarinen, System development methodology and project success, Information and Management 19 (3), 1990, pp. 183-193.]]
[54]
{54} R. Schmidt, K. Lyytinen, M. Keil, P. Cule, Identifying software project risks: an international Delphi study, Journal of Management Information Systems 17 (4), 2001, pp. 5-36.]]
[55]
{55} P. Tait, I. Vessey, The effect of user involvement on system success: a contingency approach, MIS Quarterly (March 1988) 91-110.]]
[56]
{56} D. Tapscott, D. Ticoll, A. Lowy, Digital Capital: Harnessing the Power of Business Webs, Harvard Business School Press, Boston, 2000.]]
[57]
{57} S. Taylor, P.A. Todd, Understanding information technology usage: a test of competing models, Information Systems Research 6 (2), 1995, pp. 144-176.]]
[58]
{58} R.H. Thayer, J.H. Lehman, Software engineering project management: a survey concerning US aerospace industry management of software development projects, in: D.J. Reifer (Ed.), Software Management, IEEE Computer Society Press, Washington, DC, 1979, pp. 337-354.]]
[59]
{59} R.H. Thayer, A. Pyster, R.C. Wood, The challenge of software engineering project management, IEEE Computer 13 (8), (August 1980) 51-59.]]
[60]
{60} L. Wallace, The development of an instrument to measure software project risk, unpublished Doctoral Dissertation, Georgia State University, 1999.]]
[61]
{61} S. Ward, Requirements for an effective project risk management process, Project Management Journal 30 (3), 1999, pp. 37-43.]]
[62]
{62} R.W. Zmud, Management of large software development efforts, MIS Quarterly 4 (2), 1980, pp. 45-55.]]

Cited By

View all
  • (2024)A Proposed Model for Embedding Risk Proportion in Software Development Effort EstimationProcedia Computer Science10.1016/j.procs.2024.03.185234:C(1777-1784)Online publication date: 17-Jul-2024
  • (2022)Examining the Critical Success Factors in IT ProjectsInternational Journal of Information Technology Project Management10.4018/IJITPM.29042313:1(1-38)Online publication date: 31-Jan-2022
  • (2022)Recovering Troubled IT Projects: The Roles of Transformational Leadership and Project ComplexityInformation Systems Frontiers10.1007/s10796-020-10068-724:1(233-245)Online publication date: 1-Feb-2022
  • Show More Cited By

Recommendations

Comments

Information & Contributors

Information

Published In

cover image Information and Management
Information and Management  Volume 42, Issue 1
December 2004
250 pages

Publisher

Elsevier Science Publishers B. V.

Netherlands

Publication History

Published: 01 December 2004

Author Tags

  1. cluster analysis
  2. outsourcing
  3. project management
  4. scope
  5. software project risk

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 30 Aug 2024

Other Metrics

Citations

Cited By

View all
  • (2024)A Proposed Model for Embedding Risk Proportion in Software Development Effort EstimationProcedia Computer Science10.1016/j.procs.2024.03.185234:C(1777-1784)Online publication date: 17-Jul-2024
  • (2022)Examining the Critical Success Factors in IT ProjectsInternational Journal of Information Technology Project Management10.4018/IJITPM.29042313:1(1-38)Online publication date: 31-Jan-2022
  • (2022)Recovering Troubled IT Projects: The Roles of Transformational Leadership and Project ComplexityInformation Systems Frontiers10.1007/s10796-020-10068-724:1(233-245)Online publication date: 1-Feb-2022
  • (2021)Development of Rule-Based Software Risk Assessment and Management Method with Fuzzy Inference SystemScientific Programming10.1155/2021/55321972021Online publication date: 1-Jan-2021
  • (2021)Modeling team dynamics for the characterization and prediction of delays in user storiesProceedings of the 36th IEEE/ACM International Conference on Automated Software Engineering10.1109/ASE51524.2021.9678939(991-1002)Online publication date: 15-Nov-2021
  • (2021)Modeling cultures of the embedded software industry: feedback from the fieldSoftware and Systems Modeling (SoSyM)10.1007/s10270-020-00810-920:2(447-467)Online publication date: 1-Apr-2021
  • (2021)Designing a Risk Assessment Tool for Artificial Intelligence SystemsThe Next Wave of Sociotechnical Design10.1007/978-3-030-82405-1_32(328-339)Online publication date: 4-Aug-2021
  • (2020)Identifying Usability Risks for Mobile ApplicationProceedings of the 2020 International Conference on Engineering and Information Technology for Sustainable Industry10.1145/3429789.3429813(1-6)Online publication date: 28-Sep-2020
  • (2020)Exploring the industry's challenges in software testingJournal of Software: Evolution and Process10.1002/smr.225132:8Online publication date: 3-Aug-2020
  • (2019)Patterns of Effort Contribution and Demand and User Classification based on Participation Patterns in NPM EcosystemProceedings of the Fifteenth International Conference on Predictive Models and Data Analytics in Software Engineering10.1145/3345629.3345634(36-45)Online publication date: 18-Sep-2019
  • Show More Cited By

View Options

View options

Get Access

Login options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media