Activity: Confirm Duplicate
or Rejected CR
Purpose
|
| Role: Change Control Manager |
| Frequency: Once a configuration item has been baselined and entered into the configuration management system, all requests to changes to it should go through the official change request management process. |
| Steps
|
| Input Artifacts:
| Resulting Artifacts:
|
| Tool Mentors:
|
| Workflow Details:
|
Retrieve the Change Request Form
The Change Request Form is a formally submitted artifact that is used to track all requests (including new features, enhancement requests, defects, changed requirements, etc.) along with related status information throughout the project lifecycle. All change history will be maintained with the CR, including all state changes along with dates and reasons for the change. This information will be available for any repeat reviews and for final closing. An example Change Request Form is provided in Artifact: Change Requests.
Confirm Duplication or Validity
If a CR is suspected by the CCB of being a Duplicate or Rejected as an invalid request (e.g., operator error, not reproducible, the way it works, etc.), a delegate of the CCB is assigned to confirm the duplicate or rejected CR and to gather more information from the submitter, if necessary.
If insufficient data exists to confirm the validity of a Rejected or Duplicate CR, The owner automatically gets changed to the submitter who is notified to provide more data (More Info).
Update the Change Request Status
Based on the results of the investigation, one of the following should occur:
- The confirmed duplicate or rejected Change Request should be Closed (and the submitter notified),
- More information is requested from the submitter (More Info), or
- The Change Request information is updated to show why it is not a duplicate or invalid request and re-Submitted for CCB Review.
Typical states that a Change Request may pass through are shown in Concepts: Change Request Management)
