How time management affects a Cloud ERP Project

There are a few specific things to note when you're planning the amount of timerequired of you or your team members for a Cloud ERP implementation.

Schedule:

In most cases where the consulting team is organized and well-planned, there will be an implementation or project schedule.  An accurate and well thought-out schedule should be followed during the implementation. This allows people to plan daily work requirements as well as additional project requirements from the schedule and allows every team member to know where in the implementation process they are.

Take Charge:

Be the person that understands all of the elements of the project;  the point of contact that everyone relies upon throughout the project. Enforce the schedule and be a champion for it. This schedule is the "key" to the implementation rolling to a successful completion as intended.

Scope of Work/Budget Requirements:

Know the project scope of work well. This allows you to contribute to the implementation process by staying within the agreed scope of work, the project budget and in aiding the consulting partner to better configure and implement the ERP solution with little unforeseen delays. If you don't know the project scope and budget, then how can you manage your time efficiently and stay within the budget allocated to the project?

Backup Plan:

Have a good backup plan to address potential changes you could face during a project. This will allow you to effectively stay on course, on budget by utilizing Scope of Work and Budget as the project goes.   Problems during every project is almost inevitable, so having a way to switch to an alternate plan when necessary goes a long way in keeping the project on track.

Backseat Driver:

One of the biggest resource drain and project slowing hogs is the "backseat driver". This is someone who, at the kickoff of the project was not at all involved or even a participant. But at the point where something starts to go "off track" with the project of any significance, the "backseat driver" shows up to direct everyone with their solution to the issue. Their only contribution to the project at that point to slow it, since they hadn't been involved at the start of the project.  You will not be anyone's favorite by being a backseat driver. Staying involved throughout the implementation, being a constant contributor and not a cause of delays will have you guiding the project smoothly to completion from the driver's seat. No matter how small the issue may be, stay a part of it. Every small issue of the project is as important to the larger end result as are the bigger things. 

Cliff Hall