aggressive project management processes

Make the best use of consultants' knowledge
This is the fourth and final part of article on Success factors of an ERP implementation. We are sure this series of articles will guide our readers make their ERP system work effectively and successfully.
Implement aggressive project management processes: The magnitude of an ERP implementation requires aggressive and structured project management processes. An ERP implementation is complex and touches virtually everyone in the organization. Without the structure of project management processes and without a project manager who understands this methodology, the project runs significant risk in time, quality and costs. "Go-live" dates could be missed and the credibility of the project team and the ERP software itself could suffer dramatically.
Create a project organization structure to provide planning and quick response for decision-making and issues management: The toughest problems with any project implementation involve people issues. Pre-project planning must include the creation of clearly defined roles and responsibilities. The following critical roles need to be filled by qualified people: project sponsor, project director and/or project manager, functional team leaders, technical team leaders, project coordinator/scheduler, etc. These people must have dedicated time to the project and they must be willing to be accountable for dealing with issues and making timely decisions. Many ERP implementations become paralyzed when issues are put on hold and are not dealt with quickly.
Make the best use of the external consultants and experts: These people are paid huge amounts of money for helping you in implementing the ERP system. So you must make the best use of their knowledge and skills and ensure that the knowledge transfer is complete before they leave the project.
Teach the organization to use new capabilities: The natural progression from building capabilities is actually using them. While this may sound obvious, many organizations are far better at building new capabilities than at teaching (and motivating) people to use them. Successful companies avoid this fundamental imbalance. For them teaching goes hand-in-hand with building new capabilities, from defining roles to developing skills to culture shifts.
Implementation review: This review must be performed after users are competent with the system. The goal is to ask the software vendor to suggest better ways to use the system.
Assign clear ownership of benefits: During implementation, it is usually clear that the responsibility for going live-on-time and on budget-ultimately belongs to one person, the project leader. But after going live, who owns the benefits that are being targeted? In many companies, this is a difficult question to answer - no one is identified as the owner. But in successful companies accountability for results is no mystery. The owner may be the business unit leader, a project sponsor, a process owner or someone else. What is important is that there is somebody whose responsibility is realizing the benefits.
For more information kindly
visit:http://www.erppandit.com/Make-the-best-use-of-consultants-knowledge.html