Merrill Warkentin
Robert S. Moore
Abstract
Information systems development projects are a significant expenditure of time, effort and money for many enterprises. Historically it has been estimated that 50-80% of projects fail to achieve their objectives for a variety of reasons. Researchers have identified numerous factors associated with system development failure. In this paper, we first synthesize the vast research regarding systems development risk factors and provide a framework that illustrates interactions between risk factors. The framework was used to develop an open-ended questionnaire that was answered by an inter-industry group of experienced systems development engineers and project managers. Analysis of their reports indicates that experienced professionals perceive that all risk factors (technical, resource, etc.) ultimately derive from organizationally-oriented factors, to be solved with organizational responses. This holistic viewpoint of risk assessment is counter to that of systems professionals more involved in day-to-day development decision making. For these developers, risks are more likely to be characterized as fitting into traditional discrete categories. This apparent dichotomy of risk importance was further investigated through an intra-organizational study which directly assessed how professionals recognize and treat risks in the development process. Results illustrate that a successful project environment may be characterised as one in which all systems professionals maintain a holistic view of organizational risk and that organizational culture, as opposed to experience, may predicate such an environment. Implications and future research directions are discussed.
- Al-Mushayt, O., Doherty, N. and King, M. (2001) An investigation into the relative success of alternative approaches to the treatment of organizational issues in systems development projects. Organization Development Journal 19(1), 31--48.Google Scholar
- Al-Shehab, A.J., Hughesm R.T. and Winstanley, G. (2005) Modelling risks in IS/IT projects through causal and cognitive mapping. The Electronic Journal of Information Systems Evaluation 8(1), 1--10.Google Scholar
- Alter, S. (1979) Implementation risk analysis. TIMS Studies in Management Sciences 13(2), 103--119.Google Scholar
- Alter, S., and Ginzberg, M. (1978) Managing uncertainty in MIS implementation. Sloan Management Review 20(1), 23--31.Google Scholar
- Armour, P.G. (2005) To plan, two plans: A planning approach to managing risk. Communications of the ACM 48(9), 15--19. Google ScholarDigital Library
- Barki, H., Rivard, S., and Talbot, J. (1993) Toward an assessment of software development risk. Journal of Management Information Systems 10(2), 203--225. Google ScholarDigital Library
- Barki, H., Rivard, S., and Talbot, J. (2001) An integrative contingency model of software project risk management. Journal of Management Information Systems 17(4), 37--69. Google ScholarDigital Library
- Bednarz, A. (2002) IT Malpractice, available at http://www.nwfusion.com/careers/2002/0408man.html, accessed October 3, 2002, Network World Fusion.Google Scholar
- Clegg, C., Axtell, C., Damodaran, L., Farbey, B., Hull, R., Lloyd-Jones, R., Nicholls, J., Sell, R, and Tomlinson, C. (1997) Information technology: A study of performance and the role of human and organizational factors. Ergonomics 40(9), 851--871.Google ScholarCross Ref
- Doherty, N.F. and King, M. (1998) The consideration of organisational issues during the systems development process: An empirical analysis. Behaviour & Information Technology 17(1), 41--51.Google Scholar
- Doherty, N.F. and King, M. (2001a) An investigation of the factors affecting the successful treatment of organisational issues in systems development projects. European Journal of Information Systems 10(4), 147--160. Google ScholarDigital Library
- Doherty, N.F. and King, M. (2001b) The treatment of organisational issues in systems development projects: The implications for the evaluation of information technology investments. The Electronic Journal of Information Systems Evaluation 4(1), 1--14.Google Scholar
- Doherty, N.F. and King, M. (2003) From technical change to socio-technical change: Towards a proactive approach to the treatment of organisational issues. In Socio-technical and human cognition elements of information systems (CLARKE S, COAKES E, HUNTER G and WENN A, Eds), pp 22--40, Idea Group Publishing, Hershey, PA. Google ScholarDigital Library
- Doherty, N.F. and King, M. (2005) From technical to socio-technical change: Tackling the human and organizational aspects of systems development projects. European Journal of Information Systems 14, 1--5. Google ScholarDigital Library
- Doherty, N.F. and King, M., and Al-Mushayt, O. (2003) The impact of inadequacies in the treatment of organizational issues on information systems development projects. Information & Management 41(1), 49--62. Google ScholarDigital Library
- Ewusi-Mensah, K. (2003) Software development failures. The MIT Press, Cambridge, MA. Google ScholarDigital Library
- Ewusi-Mensah, K. and Przasnyski, Z.H. (1994) Factors contributing to the abandonment of information systems development projects. Journal of Information Technology 9(3), 185--201.Google ScholarCross Ref
- Faraj, S. and Sambamurthy, V. (2006) Leadership of information systems development projects. IEEE Transactions of Engineering Management 53(2), 238--249.Google ScholarCross Ref
- Gotterbarn, D. and Rogerson, S. (2005) Responsible risk analysis for software development: Creating the software development impact statement. Communications of the AIS 15, Article 40, 730--750.Google Scholar
- Haber, L. (2003) How do you measure ITSM success?, available at http://itmanagement.earthweb.com/service/print.php/3291421, accessed April 2, 2004, Jupitermedia Corporation.Google Scholar
- Hayes, L. (2005) Development study: Haste makes waste, available at http://www.computerworld.com/developmenttopics/development/story/0,10801,104846,00.html, accessed October 6, 2005, Computerworld.Google Scholar
- Hornby, C., Clegg, C., Robson, C., McClaren, J., Richardson, C., and O'Brien, P. (1992) Human & organisational issues in information systems development. Behaviour & Information Technology 11(3), 160--174.Google Scholar
- Jiang, J.J., Klein, G., and DIscenza, R. (2001) Information systems success as impacted by risks and development strategies. IEEE Transactions on Engineering Management 48(1), 46--55.Google ScholarCross Ref
- Keil, M., Tan, B.C.Y., Wei, K., Saarinen, T., Tuunainen, V., and Wassenaar, V. (2000) A cross-cultural study on escalation of commitment behavior in software projects. MIS Quarterly 24(2), 299--325. Google ScholarDigital Library
- Keil, M., Im, G.P., and Mahring, M. (2007) Reporting bad news on software projects: The effects of culturally constituted views of face-saving. Information Systems Journal 17(1), 59--87.Google ScholarCross Ref
- Laudise, T.M. and Nuara, L.T. (2002) How to contract for a successful e-commerce development project: Beating the odds. The Business Lawyer 58, 299--316.Google Scholar
- Lucas, H.C. (1975) Why information systems fail. Columbia University Press, New York.Google Scholar
- Lyytinen, K., Mathiassen, L. and Ropponen, J. (1998) Attention shaping and software risk -- a categorical analysis of four classical risk management approaches. Information Systems Research 9(3), 233--255. Google ScholarDigital Library
- Lyytinen, K. and Robey, D. (1999) Learning failure in information systems development. Information Systems Journal 9(2), 85--101.Google ScholarCross Ref
- McFarlan, F.W. (1981) Portfolio approach to information systems. Harvard Business Review 59(5), 142--150.Google Scholar
- McGraw, G. (2002) Managing software security risks. IEEE Computer 35(4), 99--101. Google ScholarDigital Library
- Morgan, R.M. and Hunt, S.D. (1994) The commitment-trust theory of relationship marketing. Journal of Marketing 58(3), 20--38.Google ScholarCross Ref
- Nelson, R.R. (2007) IT project management: Infamous failures, classic mistakes, and best practices. MIS Quarterly Executive 6(2), 67--78.Google Scholar
- Ropponen, J. and Lyytinen, K. (2000) Components of software development risk: How to address them? A project mananger study. IEEE Transactions on Software Engineering 26(2), 98--112. Google ScholarDigital Library
- Schmidt, R., Lyytinen, K., Keil, M., and Cule, P. (2001) Identifying software project risks: An international Delphi study. Journal of Management Information Systems 17(4), 37--69. Google ScholarDigital Library
- Segars, A.H. and Grover, V. (1996) Designing company-wide information systems: Risk factors and coping strategies. Long Range Planning 29(3), 381--392.Google ScholarCross Ref
- Sherer, S.A. and Alter, S. (2004) Information system risk and risk factors: Are they mostly about information systems? Communications of the AIS 14, 29--64.Google Scholar
- Snow, A.P., Keil, M., and Wallace, L. (2007) The effects of optimistic and pessimistic biasing on software project status reporting. Information and Management 44(2), 130--141. Google ScholarDigital Library
- Songini, M. (2005) Software ownership battle adds 10m to cost of 'Big Dig'. Computerworld 39(9), 16.Google Scholar
- Standish Group International. (1995) The chaos report (1994), available at http://www.standishgroup.com/sample_research/PDFpages/chaos1994.pdf, accessed March 23, 2004, The Standish Group International.Google Scholar
- Standish Group International. (1999) Chaos: A recipe for success (1999), available at http://www.standishgroup.com/sample_research/PDFpages/chaos1999.pdf, accessed March 23, 2004, The Standish Group International.Google Scholar
- Standish Group International. (2001) Extreme chaos (2001), available at http://www.standishgroup.com/sample_research/PDFpages/extreme_chaos.pdf, accessed March 23, 2004, The Standish Group International.Google Scholar
- Standish Group International. (2003) Chaos Chronicles, Version 3.0, available at http://www.standishgroup.com/chaos_resources/chronicles.php, accessed November 15, 2007, The Standish Group International.Google Scholar
- Stephen, D., Keil, M., Mathiassen, M., Shen, Y., and Tiwana, A. (2007) Attention-shaping tools, expertise, and perceived control in IT project risk assessment. Decision Support Systems 43(1), 269--283. Google ScholarDigital Library
- Tiwana, A. and Keil, M (2004) The one-minute risk assessment tool. Communications of the ACM 47(11), 73--77. Google ScholarDigital Library
- Tiwana, A. and Keil, M. (2006) Functionality risk in information systems development: An empirical investigation. IEEE Transactions on Engineering Management 53(3), 412--425.Google ScholarCross Ref
- Wallace, L.G. (1999) The development of an instrument to measure software project risk. Ph.D Thesis, College of Business Administration, Georgia State University. Google ScholarDigital Library
- Wallace, L.G., Keil, M., and Rai, A. (2004) Understanding software project risk: A cluster analysis. Information and Management 42(1), 115--125. Google ScholarDigital Library
- Webster, B.F. (2000) Patterns in IT litigation: Systems failure (1976-2000). A Study by Pricewaterhouse Coopers LLP.Google Scholar
Index Terms
- Analysis of systems development project risks: an integrative framework
Recommendations
Information Technology Project Outcomes: An Exploratory Study of Project Managers' Viewpoints
Enterprise IT projects can end up costing much more than initial estimations, taking much longer time than expected or delivering benefits below expectations. The success or failure of IT projects, however, depends on the project managers. Many reasons ...
Technology Related Risks on Virtual Software Development Projects
Virtual software development projects have a greater reliance on technology than traditional co-located projects because of the need to leverage technology to facilitate or enhance communication among virtual team members. The goal of this research was ...
Surveying the Risks and Benefits of IT Outsourcing
In a global economy fueled by advances in telecommunications and information technologies, offshore outsourcing is evolving from conventional international-trade practices. Today, companies are looking at all their business activities with an eye toward ...
Comments