Sample Thesis Paper
Cotteleer (2003) completed extensive case studies of ERP implementation failures over the last decades. Amongst these failures are the Hershley inability to deliver candy during Halloween party; Nike slump in orders and finally, Foxmeyer’s inability to meet orders. In most of these case study failures, over two thirds fell short of their goals (Majed, 2000). Outright failures were reported by Langenwalter (2000) in half of the ERP implementation projects, whereas Bulkelery (1996) cited failures resulting to the firms’ bankruptcy. Various ERP implementers differ in their definitions of failure, such as down time of systems (Deutsch , 1998), partial utility of the system, reduction in business stakes (Diederish, 1998) decline in market values, declined in competitive advantage and subsequent market share (Nelson and Ramstad, 1999). However, one of the deepest perceptions of ERP implementation failure was presented by Ptak (2000) who asserted that inability meet Return On Investment from the commencement of the project with a failure statistic averaging 75%.
In modern time, the number of ERP implementation failures has been rising to the disadvantage of the business entities (Chen et al. 2009). Whereas some business has systems to audit the causes of the failures, other lacks this important tool (Wong et al. 2005). Markus et al, (2000) preferred the life cycle even though this approach is reactive after the failures. Never the less, the life cycle approach succeeded in diagnosing the problem at every stage. Past studies by Lyytinen (1988) relied on the Information System implementation steps to establish courses for failures, also know as the Critical Failure Factors (CFF) (Wong et al. 2005).