Q.3 Imagine that in the ERP implementation you are involved with, users that are reluctant to get involved with phase 2. What issues, problems and risks, both short and long term, does this present?

In any ERP implementation project, there will be many people assigned to the project. Involving users in your ERP project phases, said Andy Klee, president of Klee Associates, Inc., a consulting firm in Cedaredge, Colo. “The software is not going to do you much good if you don’t have employee buy-in,” he added. Involving users than just top management in the decision implementation planning process will go a long way to make users feel more ownership, which will reduce end-user resistance in the future. Resistance is the primary reason why so many projects fail. According to Lozinsky (1998, p71), ‘phase 2 is the most critical phase because during its development all concept associated with the operation of the software package will be defined. If users are reluctant to get involved with phase 2, it may cause delay an ERP implementation’s project or project failure.

Way to minimise the end-user resistance:

• Give more training to key users
• Get users involved as much as possible

 Short and long term problems arising due to reluctant users could be the following:Short Term:

• User may have a fear of the new system
• The fear may cause users won’t cooperate with the work team
• User will influent each other in negative way which will cause delay ERP implementation
• An organisation will cost more money due to the delay ERP implementation
• The lack of the communication will increase conflict between users and project team

Long Term:

• The goal of the project will fail
• An organisation will lost million of moneys and resources
• An organisation may need to hired a external consultants advice
• An organisation may lost customers and can not make more money

Following on from the previous two weeks provide a rough draft of your introduction and your executive summary. Dot points are fine.

Introduction:

• Background information of CQU
• The aim of the CQU case report
• The scope of the report which give an overview of the content of the report

 Executive summary:

• The background of the case study (CQU)
• Provide clear guidelines and recommendations on what direction CQU should take with their ERP system
• The recommendations for CQU should continue with the ERP or stop the ERP or other options

Reference:

Lozinsky, S 1998, Enterprise wide software solutions, 1st edn, Addison Wesley.