Task: Review Change Request |
This task defines how to perform change request triage.
Disciplines: Configuration and Change Management
Purpose
The purpose of this task is to determine if the change request should be accepted or rejected, and to define how to perform a change request triage.
Relationships
Roles | Primary Performer: Change Control Manager | Additional Performers:
Inputs | Mandatory: Change Request | Optional: None
Outputs | Change Request
Main Description
In this task, the change request is verified to ensure that it comes from an acceptable source, that it is clearly understood, and that it is within scope. Then the change request is analyzed for its potential impact on the development. If necessary, create child change requests to handle detail.
Steps
Verify the change request
Who has issued the change request? Do you understand the change request? If not, get more information from the Change Request Submitter. Does it apply to your product or responsibility? If not, inform the Submitter. Categorize the change request (enhancement, defect, and so on).
Analyze the impact of the change request
Perform (or delegate) an overall impact assessment (which artifacts are affected: requirement impact, design impact, implementation impact, and so on). Is there sufficient basis to justify the change request? Does the business case exist? Inform the appropriate decision maker and seek approval to perform the work.
Create child change requests, if necessary
In some cases, it is necessary to create child change requests to handle all of the detail of a requested change.
Alternatives
In some cases, it is necessary to create child change requests to handle all of the details of a requested change.
More Information
Guidelines | Review Change Request
Tool Mentors | Reviewing a Change Request Using Rational ClearQuest
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.