Skip to main content Accessibility help
×
Home
  • Get access
    Check if you have access via personal or institutional login
  • Cited by 3
  • Print publication year: 2003
  • Online publication date: February 2012

5 - Enterprise System Implementation Risks and Controls

from Part II - From Risks to Critical Success Factors

Summary

Introduction

Some organizations report success and significant process gains resulting from enterprise system implementation, while many others encounter significant losses. It is readily apparent that the implementation of packaged enterprise system software, and associated requisite changes in business processes, has proved not to be an easy task. As many organizations have discovered, the implementation of enterprise systems can become a recipe for disaster unless the process is carefully handled. The following headlines provide a glimpse of the troubles encountered by organizations, ‘SAP: Whirlpool's Rush to Go Live Led to Shipping Snafus’ (Collett, 1999), ‘Delays, Bugs, and Cost Overruns Plague PeopleSoft's Services’ (Olsen, 1999) ‘ERP Project Leads to Court Fight’ (Stedman, 1999) and ‘PeopleSoft Problems Persist, Cleveland State Looks for a New Project Manager’ (Olsen, 2000). In 1995, US firms incurred an estimated $59 million in cost overruns on information system projects and another $81 million on cancelled software projects (Johnson, 1995). Furthermore, it is estimated that approximately 90% of enterprise system implementations are late or over budget (Martin, 1998).

Enterprise system (ES) implementations are different from ‘traditional’ system analysis and design projects (Davenport, 2000). Among the significant differences are the scale, complexity, organizational impact, and the costs of ES projects and subsequent business impact if the project does not succeed. An ES implementation impacts the entire organization, whereas a traditional project impacts often only a limited area of the organization. Furthermore, ES projects are often associated with the reengineering of business practices.

Related content

Powered by UNSILO
References
Arnold, V., Hunton, J. E., and Sutton, S. G. (2000) On the Death and Dying of Originality in the Workplace: A Critical View of Enterprise Resource Planning Systems' Impact on Workers and the Work Environment. Working Paper, University of South Florida
Anderson, J. and Narasumhan, R. (1979) Assessing Implementation Risk: A Technological Approach. Management Science, 25(6), 512–521
Appleton, E. (1999) How to Survive ERP. Datamation, March
Arens, A. A. and Loebbecke, J. K. (1997) Auditing: An Integrated Approach. Upper Saddle River, NJ: Prentice-Hall
Attewell, P. (1992) Technology Diffusion and Organisational Learning: The Case of Business Computing. Organisation Science, 1(2), 1–19
Barki, H., Rivard, S., and Talbot, J. (1993) Toward an Assessment of Software Development Risk. Journal of Management Information Systems, 10(2), 203–225
Best, C. (1997) Integrated System Builds on Human Foundation, Computing Canada, 23, December
Bingi, P., Sharma, M., and Godla, J. (1999) Critical Issues Affecting an ERP Implementation. Information Systems Management, 16(3), 7–14
Bowen, T. (1998) Committing to Consultants: Outside Help Requires Internal Commitment and Management Skills. Info World
Brockner, J. (1992) The Escalation of Commitment towards a Failing Course of Action: Towards Theoretical Progress. Academy of Management Review, 17(1), 39–61
Callaway, E. (1997) ERP: Test for Success. PC Week online, 22 December
Cameron, D. and Meyer, L. (1998) Rapid ERP Implementation – A Contradiction. Management Accounting (USA), 80(6), 56–60
Clemons, C. (1998) Successful Implementation of an Enterprise System: A Case Study. Proceedings of the AIS Conference Americans. Baltmore Maryland: Association for Information Systems, pp. 109–110
Collett, S. (1999) SAP: Whirlpool's Rush to Go Live Led to Shipping Snafus. Computerworld Online News. http://www.computerworld.com/cwi/story/0,1199,NAV47_STO29365,00.html
Davenport, T. (1998) Putting the Enterprise into the Enterprise System. Harvard Business Review, 76(4), 121–133
Davenport, T. (2000) Mission Critical: Realizing the Promise of Enterprise Systems. Boston, MA: Harvard Business School Press
Deutsch, C. H. (1998) Some Tips on Avoiding the Pain. The New York Times, 8 November
Glover, S. M., Prawitt, D., and Romney, M. (1999) Implementing ERP. Internal Auditor, 40–47
Grabski, S., Leech, S. and Lu, B. (2001) Risks and Controls in the Implementation of ERP Systems, 1(1), 1–29
Hammer, M. (1990) Reengineering Work: Don't Automate. Obliterate, Harvard Business Review, 68(4), 104–112
Hammer, M. and Champy, J. (1993) Reengineering the Corporation: A Manifesto for Business Revolution. New York: Harper Business
Holland, C. and Light, B. (1999) Critical Success Factors Model for ERP Implementation. IEEE Software, 16(3), 30–36
Jiang, J. J. and Klein, G. (1999) Risks to Different Aspects of System Success. Information and Management 36, 263–272
Jiang, J., Klein, G. and Balloun, J. (1996) Ranking of System Implementation Success Factors. Project Management Journal, 27(4), 50–55
Johnson, J. (1995) The Dollar Drain of IT Project Failures. Application Development Trends, 2(1), 41–47
Kanodia, C., Bushman, R., and Dickhaut, J. (1989) Escalation Errors and the Sunk Cost Effect: An Explanation Based on Reputation and Information Asymmetries. Journal of Accounting Research, 27(1), 59–77
Kay, E. (1999) Desperately Seeking SAP Support, Datamation, March
Keil, M. (1995) Pulling the Plug: Software Project Management and the Problem of Project Escalation. MIS Quarterly, 19(4), 421–447
Martin, M. (1998) An ERP Strategy. Fortune, 2 February, 95–97
McFarlan, F. (1981) Portfolio Approach to Information Systems. Harvard Business Review, 59(5), 142–150
McKie, S. (1998) Packaged Solution or Pandora's Box? Intelligent Enterprise, November, 39–43
Olsen, F. (1999) Delays, Bugs, and Cost Overruns Plague PeopleSoft's Services. The Chronicle of Higher Education, 24 September, A32, A33–34, A36
Olsen, F. (2000) PeopleSoft Problems Persist, Cleveland State Looks for a New Project Manager. The Chronicle of Higher Education, 4 February, A49
Raghunathan, B. and Raghunathan, T. (1998) Impact of Top Management Support on IS Planning. Journal of Information Systems, 12(1), 15–23
Reel, J. (1999) Critical Success Factors in Software Projects. IEEE Software, 16(3), 18–33
Scott, J. (1999) The FoxMeyer Drugs' Bankruptcy: Was It a Failure of ERP? Proceedings of AMCIS 1999 Americas Conference on Information Systems, 223–225
Sharp, D. and Salter, S. (1997) Project Escalation and Sunk Costs: A Test of the International Generalizability of Agency and Prospect Theories. Journal of International Business, 28(1), 101–122
Staw, B. (1976) Knee-Deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action. Organizational Behavior and Human Performance, 16(1), 27–44
Staw, B. (1981) The Escalation of Commitment to a Course of Action. Academy of Management Review, 6(4), 577–587
Staw, B. and Ross, J. (1987) Behavior in Escalations Decisions: Antecedents, Prototypes, and Solutions. In Research In Organizational Behavior, Cummings, L. L. and Staw, B. (Eds), Greenwich, CT: JAI Press
Stedman, C. (1999) ERP Project Leads to Court Fight. Computerworld Online News. http://www.computerworld.com/cwi/story/0,1199,NAV47_STO36333,00.html
Whitten, J. and Bentley, L. (1998) Systems Analysis and Design Methods, 4th edn. Boston, MA: Irwin/McGraw-Hill
Yin, R. K. (1994) Case Study Research, Design and Methods, 2nd edn. Sage Publications
Zmud, R. W. (1980) Management of Large Software Development Efforts. MIS Quarterly, 4(2), 45–55