IT Project Implementation Failures HCS/245 September 16th, 2013 Marc Magill Project Implementation A typical IT Implementation process normally follows SDLC process. SDLC refers to Standard Development Life-Cycle. Below are the standard SDLC phases: 1) Initiation Phase 2) System Concept Development 3) Planning 4) Requirements Analysis 5) Design 6) Development 7) Integration & Testing 8) Implementation 9) Operations & Maintenance 10) Disposition Any project starts
Words: 803 - Pages: 4
An enterprise resource planning (ERP) system is a set of core software modules that enable organizations to share data across the entire enterprise through the use of a common database and management reporting tools. The goal is to enable easy access to business data and to create efficient, streamlined work processes. Origin of "ERP" In 1990 Gartner Group first employed the acronym ERP as an extension of material requirements planning (MRP), later manufacturing resource planning and computer-integrated
Words: 1689 - Pages: 7
Case Study This is a case study of Memorial Health System’s CPOE implementation. There are several factors that contributed to the implementation’s failure. We will discuss them here, and what could have been done instead to help the project succeed instead of fail. Lack of Belief in the Project Members of the organization do not see the need for change, and are resistant to it. They feel the project is more of a hassle than a help, and will cause them problems (Wager, Lee, & Glaser, 2009)
Words: 1590 - Pages: 7
SYSTEMS IMPLEMENTATIONS Judy E. Scott and Iris Vessey T wo companies were R/3 at a new warehouse. FoxMeyer at risk. One survived expected to save $40–$50 million dollars while the other failed annually from the project, as well as to What after installing an grow rapidly and gain market share [5]. determines enterprise system FoxMeyer’s plans did not work out. (ES), SAP R/3. At the After its major customer, Phar-Mor, if a system time of its R/3 imple- implementation went bankrupt
Words: 5692 - Pages: 23
Table of Contents Introduction 3 Purpose and aims 3 Research questions 4 Significance 4 Project design 5 Project plan 5 Planning 6 Analysis of use requirements 6 Design 6 Implementation 7 Testing 7 User training 7 Deployment 8 Maintenance/ on-going support 8 Risk assessment 11 Timeline Slippage 11 Additional costs 11 Lack of full commitment by team members 11 Conflicts among team members 11 Failure of equipment 12 Late change requests 12 Lack of required expertise 12 Risks analysis matrix 12
Words: 2791 - Pages: 12
system within the federal government. These lessons can be applied to any accounting information system project. Others have developed their own recommendations for best practices and lessons learned involving implementing accounting information systems. However, in order to appreciate what IBM and others are proposing, we need to apply lessons learned to a real-life situation involving the failure to implement an accounting system properly. In Apollon Smyrnis (A Football Company) & Changing the
Words: 5446 - Pages: 22
is a highly complex system and is usually associated with high costs. The implementation is a long process and may take years to complete, furthermore, the process can be delayed and disrupted by inadequate planning and execution. It is not surprising that the biggest issue in ERP is the failure of a successful implementation. Hence, a company has to understand and consider the success factors of a successful implementation before deciding on implementing an ERP system. Top management commitment
Words: 998 - Pages: 4
The FoxMeyer Drugs' Bankruptcy: Was it a Failure of ERP? Judy E. Scott, The University of Texas at Austin, Judy.Scott@bus.utexas.edu Abstract This interpretive case study of FoxMeyer Drugs' ERP implementation is based on empirical frameworks and models of software project risks and project escalation. Implications of the study offer suggestions on how to avoid ERP failure. warehouses, the transition to the first automated warehouse was a disaster. Disgruntled workers damaged inventory, and orders
Words: 2060 - Pages: 9
this project introduce the project management to monitor and control few areas of knowledge such as scope, time, cost, quality, risk, communication, procurement, etc. EXECUTIVE SUMMARY The motive of this paper is to provide information and justify the implementation of automatic baggage system project in Denver International Airport and its failure or success. As we go through the case study we will analysis the activities of the project to consider and identify the aspects of the project which
Words: 1147 - Pages: 5
The FoxMeyer Drugs' Bankruptcy: Was it a Failure of ERP? Judy E. Scott, The University of Texas at Austin, Judy.Scott@bus.utexas.edu Abstract This interpretive case study of FoxMeyer Drugs' ERP implementation is based on empirical frameworks and models of software project risks and project escalation. Implications of the study offer suggestions on how to avoid ERP failure. warehouses, the transition to the first automated warehouse was a disaster. Disgruntled workers damaged inventory, and orders
Words: 2060 - Pages: 9
