Change Request Form and Logs

Originally from UCM Central
[This template was based on the IEEE template IEEE 828.1:1990]

Change Request management is simply identification of product enhancements, the assignment, tracking and eventual resolution (closure) of these.

To save you some work - here are two paper prototypes (Form and Log), that have been used in practice, to support this activity. In the longer term however, we suggest you quickly move away from the tedium of manual paper shuffling and look seriously at automated tools ... Otherwise you will surely go Nuts.

 

Change Request Form 

Application

Enter the application/product name

Change Requested By

Enter Name. If request came from external source then enter your name and other.

Date of Change Request

Enter in date/time of request here

Change Description

Enter a summary of the change required and a reason for the change.

Change Priority

Please give change request a priority of Urgent, High, Medium or Low. 

Please Tick one:

Urgent (crucial) High (preferable) Medium (desirable) Low (optional)
       

If this change is time/date dependent then please specify this here. Note: The configuration board may amend above priority/schedules dependent on other activities.

Impact Assessment

Enter a summary of the business and technical functions that could be affected by these changes. This section should specify known risks and concerns.   

Pre Deployment Test Plan

Describe how you will test the change before deployment. Note: Testing changes will greatly reduce possibility of failures and unwanted surprises.

Roll Back Plan

Describe how a failed change could be rolled back i.e. system recovery steps.

Post Deployment Test Plan

Describe how we test whether the change was successful. 

Change Approval

Please specify whether request has been accepted or rejected. The configuration control board should make this decision.

The decision of the configuration board is that this request be:

Accepted Rejected
   

If appropriate a description of the decision taken should be described here.

Change Assignment

Specify whom this change has been assigned to for resolution.

** End of Document **

 
Change Request Log

Below is an example of the fields you might use in a minimal change request log. This could be set up in excel, word etc. Note: It is recommended that such manual forms are only used for a short interim period (i.e. until more suitable tool is selected and introduced).

 

SCM Change Request Log
Project Name: Product Name:
 
Request No: CR00001
Requested By:
Submitted:
Priority:
Approved By:
Description:
Status:
 
Request No: CR00002
Requested By:
Submitted:
Priority:
Approved By:
Description:
Status:
 
etc etc

-- PatrickEgan? - 16 Dec 2002



EditAttachPrint versionHistory: r2 < r1BacklinksRaw ViewRaw editMore topic actions