Guideline: Resolving a Change Request |
This guideline describes how to resolve a Change Request.
Relationships
Related Elements | Resolve Change Request
Main Description
### Introduction Resolving a change request is the process of recording that the development activity has been completed and unit tested for the change request, and that the associated change sets are ready for formal testing. The action of resolving the change request is typically performed by the person to whom the change request has been assigned. ### Verify artifacts associated with the change request Review the properties of the change request to ensure that all of the relevant change sets are associated with the change request. The details of this step will depend upon the configuration and change management system that you are using. However, it is important to maintain traceability between the change request, associated change sets, and ultimately the new versions of each artifact changed to realize each change set. This information will greatly simplify verification (for example, by informing testers what has changed to resolve the change request so that they can ensure appropriate test coverage). It will also simplify repair and re-work should problems be identified during testing. Finally, this information permits any destabilizing changes to be identified and potentially backed-out of the configuration to undo the change. ### Disposition change request Update the relevant attributes of the change request. Again, the details of this step will depend on the configuration and change management system being used, and the specific attributed defined. For example, you may track effort to provide management metrics. In this case, you should provide an estimate of how much time was required to resolve the change request. Finally, transition the change request to the Resolved state.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.