IT Project Implementation Failures
IT Project Implementation Failures
HCS/483- Health Care Information Systems University of Phoenix
January 13, 2014
David Reed
IT Project Implementation Failures
There are many reasons why project implementations fail. Some reasons include failure to identify company needs, failure to distinguish company needs and wants, and failure to assess technical competency of staff. Some IT projects fail prior to the actual implementation due to poor planning or lack of experience. Failing to create an efficient plan is dangerous. Many companies do not select software that meets their needs. The key to a successful project implementation is to take the time to evaluate the company’s needs and plan for success. This paper is intended to discuss five indicators for IT failure and changes that can be made to eliminate their effects.
Five Indicators for IT Failure
System implementation begins once an organization has acquired the system and continues through early stages following the go-live date. System implementation processes must be supported by the senior executive team and be viewed as an organizational priority. An implementation team must be organized when planning for the implementation of a new system. The role and function of the team is to coordinate budget plans and manage aspects of the system implementation. The implementation team must include a system champion. A system champion is someone who sees the new system as necessary to the organization in order to achieve goals this person is also well respected within the organization.
Five indicators of IT failure include organizational baggage, lack of technology stability, failure to anticipate short-term disruptions, project complexity, and lack of an appropriate reward system. According to Bharadwaj, Keil, Mahring (2009) “Although IT systems are likely to differ in the strategic value to the organization, they nevertheless cause significant disruptions to a firm’s business operations when
HCS/483- Health Care Information Systems University of Phoenix
January 13, 2014
David Reed
IT Project Implementation Failures
There are many reasons why project implementations fail. Some reasons include failure to identify company needs, failure to distinguish company needs and wants, and failure to assess technical competency of staff. Some IT projects fail prior to the actual implementation due to poor planning or lack of experience. Failing to create an efficient plan is dangerous. Many companies do not select software that meets their needs. The key to a successful project implementation is to take the time to evaluate the company’s needs and plan for success. This paper is intended to discuss five indicators for IT failure and changes that can be made to eliminate their effects.
Five Indicators for IT Failure
System implementation begins once an organization has acquired the system and continues through early stages following the go-live date. System implementation processes must be supported by the senior executive team and be viewed as an organizational priority. An implementation team must be organized when planning for the implementation of a new system. The role and function of the team is to coordinate budget plans and manage aspects of the system implementation. The implementation team must include a system champion. A system champion is someone who sees the new system as necessary to the organization in order to achieve goals this person is also well respected within the organization.
Five indicators of IT failure include organizational baggage, lack of technology stability, failure to anticipate short-term disruptions, project complexity, and lack of an appropriate reward system. According to Bharadwaj, Keil, Mahring (2009) “Although IT systems are likely to differ in the strategic value to the organization, they nevertheless cause significant disruptions to a firm’s business operations when