In last week’s ERP implementation tip, I wrote about the how project buck stops at the steering committee.
This week, I discuss how the project manager can keep the executive-level steering committee focused on the project.
In last week’s ERP implementation tip, I wrote about the how project buck stops at the steering committee.
This week, I discuss how the project manager can keep the executive-level steering committee focused on the project.
In last week’s ERP implementation tip, I explained who should be selected for the various project teams.
This week, I dig a little bit deeper into the steering committee.
To execute your business, your company has set up an organizational structure, hired the right people (hopefully), delegated responsibility and incentivized desired behaviors. Operating within a defined structure helps your business avoids chaos, and keeps the right people working towards the right goals.
In last week’s ERP implementation tip, I explained how to build a strong project core team.
This week, I discuss how to use kick-off meetings to inject momentum to the start of an ERP implementation project.
In last week’s ERP implementation tip, I explained how to effectively kick off your IT project.
I inadvertently – and somewhat ironically – omitted a key ERP implementation project phase that precedes the kick-off phase. This week, I’ll delve into that overlooked phase, which is the project planning phase.
In last week’s ERP implementation tip, I wrote about the importance of creating a turn-by-turn project roadmap.
This week, I outline 5 crucial steps to building an actionable, manageable and measurable ERP implementation project plan.
In last week’s ERP implementation tip, I laid out 5 crucial steps to building an actionable, manageable and measurable project plan.
This week, I offer some guidance on how to train the core team so that it can execute the ERP implementation project plan.
In my previous ERP implementation tip, I identified potential pockets of change resistance and discussed how an effective change management plan can drive ERP implementation success and diffuse potentially fatal project resistance.
This week, I break down six key elements of a change management plan, including the training strategy. The change management plan completes the fourth and final deliverable in the project mapping phase.
In last week’s ERP implementation tip, I described how to structure an intensive, 4-course program to train your core team on the selected ERP system.
Now, after having successfully completed its training, your core team is ready to restructure the business processes to accommodate the new ERP system. In this week’s tip, I offer some advice on process mapping as well as on managing the related change and risk issues of your ERP implementation project.
In last week’s ERP implementation tip, I offered some general advice about managing the business process mapping phase of your ERP implementation project.
The mapping phase is made up of four sub-phases, each constituting a separate project deliverable. Over the next four weeks, I will break down the each of these four deliverables, starting with the business scenario list, below.
Head Office – Canada
2 St Clair Ave W, Suite 1800
Toronto, ON M4V 1L5
+1 (866) 282-5899
+1 (647) 499-8161
[email protected]
U.S.A. Locations
Arizona
California
Texas
+1 (866) 282-5899
+1 (647) 499-8161
[email protected]