Technical Risk Management on Enterprise Integration Projects

Enterprise Integration (EI) is essential to organisations wishing to fulfill broader business objectives related to e-business, customer relationship management (CRM), supply chain management (SCM) and business-to-business (B2B) commerce. This paper describes and presents the results of a study into practices for managing technical risk on EI projects. In the study, 21 managers participated in a facilitated workshop or interview sessions to identify areas of risk (RAs) associated with EI projects and risk management practices (RMP) for addressing those RAs. Risks were identified in four separate phases in the lifecycle of an EI project, namely the strategy, planning, implementation and rollout phases. Many of the risks identified were not specific to EI projects, but were applicable to large IT projects in general. The paper is primarily concerned with technical risk although some aspects of business and organizational risk are discussed briefly.

[1]  Fred A. Cummins,et al.  Enterprise integration , 2002 .

[2]  D. Sandy Staples,et al.  New Developments in Practice I: Risk Management in Information Systems: Problems and Potential , 2001, Commun. Assoc. Inf. Syst..

[3]  David W. Stupples,et al.  Systems thinking for managing projects , 2002, IEEE International Engineering Management Conference.

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

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

[6]  Sally Wright,et al.  Information System Assurance for Enterprise Resource Planning Systems: Unique Risk Considerations , 2002, J. Inf. Syst..

[7]  Frank J. Sisti,et al.  Software Risk Evaluation Method Version 1.0. , 1994 .

[8]  G. Zsidisin Managerial Perceptions of Supply Risk , 2003 .

[9]  Donald J. Reifer Ten Deadly Risks in Internet and Intranet Software Development , 2002, IEEE Softw..

[10]  Tom Gilb,et al.  9.1.5 Risk Management: A practical toolkit for identifying, analyzing and coping with project risks , 2002 .

[11]  Deborah Buchanan,et al.  Managing process risk: planning for the booby traps ahead , 2001 .

[12]  Geoffrey G. Roy,et al.  A framework for risk analysis in software engineering , 2000, Proceedings Seventh Asia-Pacific Software Engeering Conference. APSEC 2000.

[13]  Brenda Whittaker,et al.  What went wrong? Unsuccessful information technology projects , 1999, Inf. Manag. Comput. Secur..

[14]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[15]  J. Lainhart COBIT™: A Methodology for Managing and Controlling Information and Information Technology Risks and Vulnerabilities , 2000 .

[16]  Suresh L. Konda,et al.  Taxonomy-Based Risk Identification , 1993 .

[17]  James D. McKeen,et al.  New Developments in Practice II: Enterprise Application Integration , 2002, Commun. Assoc. Inf. Syst..

[18]  Alan Weatherall,et al.  Risk identification and analysis using a group support system (GSS) , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

[19]  Mary Sumner,et al.  Risk factors in enterprise-wide/ERP projects , 2000, J. Inf. Technol..

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

[21]  Richard Turner Seven Pitfalls to Avoid in the Hunt for Best Practices , 2003, IEEE Softw..

[22]  Clive Smallman,et al.  Managing project risks: a case study from the utilities sector , 2002 .

[23]  Marian Myerson Risk management processes for software engineering models , 1996 .

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

[25]  Andrew P. Sage Risk management systems engineering , 1995, 1995 IEEE International Conference on Systems, Man and Cybernetics. Intelligent Systems for the 21st Century.

[26]  Barry W. Boehm,et al.  Software Risk Management , 1989, ESEC.

[27]  Wing Lam,et al.  An enterprise integration methodology , 2004, IT Professional.

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

[29]  S. Murthi,et al.  Preventive risk management software for software projects , 2002 .