Package Software Modifications

Description

• The identification, design and building of required modifications to purchased package software, which will enable the client to successfully implement new processes on the selected software.

Business Value

• In many cases, no package software solution will be able to satisfy every major requirement identified by a client.  Modifying the selected software in these cases can increase the likelihood of a successful implementation both by making the package more compatible with newly-designed processes and by making the package more agreeable to the user organisation in general.

Approach

The project team must be judicious in defining modifications to the package solution selected by the client.  One of the biggest advantages of purchasing packaged software is that the responsibility for maintaining and upgrading the software rests with the vendor.  The Business Organisation does not have to invest significant resources to maintain the software, as they would if a custom solution was selected.

Modifications to package software are not normally supported by the vendor, however.  If a large number of changes are required, a significant number of client resources will be needed to maintain the modifications and make them compatible with the vendor’s future software releases.

1. Compile a list of modifications to the package software (typically identified in the Detailed Process Descriptions).
1. Put in place mechanisms to evaluate and prioritise suggested modifications so that only those changes truly required to implement the software successfully are actually developed.
2. Establish a “production and testing environment” to be used during the software development process.
1. This environment not only includes the appropriate hardware, software and networks, but also databases and security-access privileges.
2. Acquire necessary equipment and software
3. Preferred development tools for the development of modifications are dependent upon the package selected and the database that the software package runs on  (e.g. Oracle, Sybase, Informix, Microsoft etc.)
4. Arrange the physical facilities
5. Install the hardware, software, and networks
6. Define the development procedures and prepare staff.
3. Develop software modifications (based on previously-defined specifications).

Guidelines

Tactics/Helpful Hints

• Since the project team must maintain a business focus during development activities, monitor these activities to ensure that “functional” requirements are being met.  If necessary, conduct frequent review sessions with users during the course of development.
• Provide adequate lead time, when establishing the production environment, to ensure that it is ready when development activities need to commence.  Confirm any lead times with vendors when acquiring necessary equipment.