Microsoft Dynamics AX is the complete ERP solution for enterprises that provides a purpose-built foundation across five industries, along with comprehensive, core ERP functionality for…
Microsoft Dynamics AX implementations face a number of risks and challenges due to the transformational impact they have on companies. Like any enterprise ERP application,…
One of the key, but often forgotten, parts of an ERP implementation is documentation. Because of the complexity of the project and all of its moving parts, it’s necessary to have a clear record of every bug fix, process change, and training class. Also, being able to show progress made and exactly what needs to happen next keeps the project on track helps to build its business case.
But what exactly do we need to document?
Imagine what would happen if the kickoff meeting for your project arrives and some of the stakeholders donâ€™t show up. You move forward with the project, thinking that theyâ€™ll get caught up. After all, as the project manager, you have deadlines to meet and you need to get started.
However, before long you start having problems with lack of communication between stakeholders and vendors. Things are being delivered at the wrong time and without meeting projects specifications – but the communication simply isnâ€™t there to fix it.
Youâ€™re constantly scrambling trying to bring everything back on schedule as quickly as possible.
Project life span is the progression of differing phases of a project. The project life span starts from the time it is conceived to the time it is completed or deemed a failure. There are six phases to the project life span:
Imagine what would happen if a small group of C-level executives got together and picked a new ERP system for your company. As an employee within the IT department, itâ€™s up to you to implement the project and make sure itâ€™s a success. You know that the C-level executives have buy-in on the project because theyâ€™re the ones who picked it, but what about the rest of the company?
Internal stakeholders can come in many forms. There are the owners, C-level executives, board members, managers, and other employees of the company that have a direct stake in the project. There are also external stakeholders that are outside the business but still need to interact with your systems. These can include customers and vendors. The faster you can get stakeholder buy-in, the smoother the implementation and strategies will go.
Nenad Simeunovic, Vice President of Services for Merit Solutions, was recently featured in the PM Network's March 2013 issue discussing using Agile Project Management techniques…