Configuration and Customisation

• List of customisation

1. Create a breakdown of the customisation areas.
2. Develop a schedule including both customisation and configuration.

• Project schedule for the phase

With the assistance of the Vendor or Implementation Partner, develop a list of the configuration required. This is typically a functional based breakdown. For example, there may be a number of configuration areas such as Sales and Distribution, HR, Payroll, Warehouse etc. Each may have a different person or team and most of the configuration can be done in parallel.

Another limitation may be the availability of support resources. The Vendor may provide one Consultant to work on the implementation and if that person needs to span several areas, the work may need to be done sequentially.

The schedule should include time for any conversion - and there may be more than one trial conversion - as well as User Acceptance Testing (UAT). There should be time built into the testing for rectification of bugs and for fixing data errors.

Where the application is to be deployed in a number of sites, consider testing of performance and availability across all sites. Just because it works in one location does not mean it will work on the other side of the country.

A key decision at this point, is how much knowledge transfer is to take place. If you intend to support the application in house, you may decide that part of the configuration will be to train your own people. This will likely extend the time - which will need to be reflected in the schedule - and may require several people work with the Consultant to understand the area. It may even require your people be sent on a training course prior to work beginning.