We ran an aggressive delivery plan in which we launched 4.5 months after starting. We knew we had condensed timescales compared to a traditional ERP implementation and so we started with a clear scoping workshop to provide a backbone to deliver against.
We knew this needed to be validated and so the team quickly stood up a development instance of the system to allow people to see it in action. We then held a range of solution workshops to refine the scope and validate the solution, by walking through the in-scope processes within IFS and agreeing any changes or requirements.
In parallel, we kicked off the data workstream which is always critical in a project like this. By mobilising this very early, we were able to prove the process to load data several times before the final cutover and also support the relevant owners of the data to iteratively improve on the data loads provided.
These informed the changes such as configurations that were needed and so the technical team were able to deliver the necessary configuration and technical elements. These were fed into the UAT process which covered the in-scope processes and any configured elements.
In parallel, we built two more environments, one for testing and one which was Production. We prioritised the changes to processes based on the number of users and this approach coupled with our condensed delivery cycle allowed us to start training and familiarisation relatively early. This meant we could provide robust training over approximately 8 weeks rather than rushing it.
ERP launches are aligned to financial periods so that the data migrated is a clean cut at a point in time. Given how important timescales were, we did attempt to launch the system after 3.5 months and whilst there was appetite, the steering board decided that a better option was to spend one more period doing further validation of some of the processes which were customer facing and also action a number of items highlighted around the time the decision was being considered.
We launched successfully at the start of August and given the scale of the change we had very little noise or negative business impact. All early life support was managed through the service desk and the small number of tickets raised were standard go-live items such as small tweaks to permissions and password resets rather than anything major.