Roles and Activities > Any Role > Update Change Request

Purpose
  • A designated CCB administrator or the assigned owner of a change request may make updates to the CR form to indicate its present state and any other relevant information.
Steps
Input Artifacts: Resulting Artifacts:
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.
Role: Any Role
More Information:

Workflow Details:

Retrieve the Change Request Form To top of page

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.

Update and Resubmit the Change Request To top of page

If more information is needed (More Info) to evaluate a CR, or if a CR is rejected at any point in the process (e.g., confirmed as a Duplicate, Reject, etc.), the submitter is notified and may update the CR with new information. The updated CR is then re-Submitted to the CCB Review Queue for consideration of the new data.

Typical states that a Change Request may pass through are shown in Concepts: Change Request Management)