Keeping the Changes on Track
By Russ Finney
Change management and control becomes a highly critical aspect of "iterative" system building throughout the construction and testing phases. A wise system builder recognizes that a change management philosophy in this situation should be very similar to that used to collect issues: when you hear it (or find it!), write it down!
- Use a form and/or a database to record any testing problems which occur either during string testing or system testing. This will provide both a problem log and a formal maintenance request for the programmer to utilize when updating the specified programs.
- Use a form and/or a database to record any newly requested features, functions, or enhancements which are revealed during the various stages of testing.
- Organize and classify all of the problem logs and change requests based on either the severity of the problem or the complexity and desirability of the enhancement.
- Review these when necessary with the appropriate project sponsors or project managers in order to obtain the appropriate authorizations before making any dramatic or time consuming changes.
Suggested Change Request Form Elements:
- Change Request Number
- Date Recorded
- Priority (Low, Medium, High)
- Date Completed
- Requested By
- Assigned To
- Change Classification
- Description of Change
- Description of Resolution
Copyright © 1999, Russ Finney, All Rights Reserved