- Business involvement - If there are multiple projects being implemented at the same time, then it is highly likely that the decision makers are not available for key milestone decisions.
- Change management - Though the requirement documents are signed off early in the scoping stage, changes to the specifications would come to light during the testing phase. This is mainly because of the lack of understanding of the new system from the business perspective. This can be avoided by involving some resources knowledgable of the new system early in the implementation cycle.
- Risk planning - Stakeholders need to keep identifying risks till the project close and project management team would need to evaluate the risks identified and work on the mitigation methods. This process need to happen iteratively throughout the implementation.
- Communication - In multi million dollar projects, normally the build/development would happen in offshore location. Projects where onsite-offshore model is adapted, need to make sure adequate communication channels are established.
- End-user training - Trained users should need to be made available for UAT. The timing of the training should match with UAT. Otherwise users trained very early would forget the learnings. Also there should not be high dependency on 1-2 key end-users.
Mar 13, 2009
Project Managemnt Pitfalls in Oracle Applications ERP implementation
Though almost all the ERP implementation projects are planned well, they are not executed with the same rigor as they were planned for. The main reasons for this lapse can be attributed to the below pitfalls:
