-
Project team members get sidetracked and project loses momentum -
The importance of implementation planning is underestimated causing implementation efforts to become uncontrolled and unfocused -
Project gets near completion, then sputters along with no final go-live and cutover -
Software selection requirements are based on current processes and existing software, rather than improved processes and new technology -
Implementation is focused too much on software; not enough on project objectives and new management practices -
Project is thought to be completed once software is installed and operational -
Software was selected based on a “perception” or a “feeling”, not based on facts -
Minor technical system difficulties stall the entire project -
Implementation efforts are primarily focused on processes with little emphasis on reporting and information needs -
Employees are asked to enter system data in their spare time
Wednesday, May 26, 2010
Top 10 reasons CMMS projects fail:
It was a cold morning in Eugene and i was going through a good website on CMMS and thought i will share this with the user.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment