Can You implement an ERP Program w/o managing it on the Project Level?
What is the best approach to implementing an ERP solution? To start the humongous change as an extensive program with all the processes designed and developed to the nth level simultaneously or to do it in phases by dividing the entire program into manageable projects with set deliverables?
Many organizations must target all system changes in all divisions/businesses. Extensive programs consist of individual programs running in parallel. It doesn't matter if 500 IT people are engaged in this implementation; the more comprehensive the scope, the blurrier it will be. They don’t consider the impacts and constraints of choosing this approach.
Requirements Finalization
Requirements finalization is one of the biggest challenges of this approach. You will find that you will never get a sign-off on completed requirements from the business. They will keep coming up with additional requirements that they need to remember because they need to consider the details of the aspect of the company. Also, there are so many aspects in the program of work to target that it’s difficult for the business to remember everything and present in a couple of workshops. The primary objective of a business representative is to run the business.
Design / Scope Freeze
Because the requirements have not yet been finalized, whenever you think you are close to completing it, you must patch it with another valid requirement to achieve the overall program objectives.
Solution Integrator Engagement
In this situation, you will need a third-party solution integrator for extended periods. This implies more money / more budget requirements.
Ultimately, you will overrun the program budget regarding cost and timelines. Even if you finish within the time and agreed-upon budget, the quality of the solution will be seriously compromised.
Training and Change Management
It is not only a challenge from a solution integration and development point of view but also another challenge to prepare your end users for such a significant change and transform them literally from ‘Zero to Hero.’ Continuous training, change management, and monitoring are required to ensure people follow the right business processes and keep the system updated with ongoing transactions.
Even with the latter approach, we can't avoid these problems. They will exist, but the scale will be much smaller and manageable. We will be able to learn from each implementation and apply those lessons to improve the following deliverable implementation.
I have learned this: Dividing the objectives of your ERP transformation program into manageable projects increases the chances of success.
Following are some key points:
- Look at the big picture, plan, design, and budget pre-approval for the overall ERP transformation program.
- Divide the whole program into set targets/projects
- Standard ERP implementation across businesses and divisions with major modules like Supply chain management, Finance, and asset management to create a basic understanding of the solution.
- Implement supporting modules like Project systems, Quality management, Human resources, transportation, etc.
- Activate specific functionality for business-specific needs, such as Mobility, RFID Scanning, and GIS system integration. Depending on the scale of the business and users, each feature can also be treated as an individual project/deliverable.
- Solution Integrators can also be engaged on a stage agreement basis. In a few years, your in-house team will be capable of running some of these projects as in-house projects.
- Change management and training will also be staged and manageable. End users will have enough time to digest one aspect of the system before starting another.
- Benefits realization will be started even before completion of the whole program using this iterative approach.




