Impact.

Recommendations and plan.

A quality review of the feasibility study is then performed to ensure that it has been conducted as requested and the final deliverable is approved and ready for release to the change approval group. All change documentation is then collated by the change manager and submitted to the change approval group for final review. This documentation includes:

The original change request form.

The approved change feasibility study report.

Any supporting documentation.

Approve Change Request

In this process, the change approval group formally reviews the change request. The change approval group chooses one of the following outcomes regarding the change proposed:

Reject the change.

Request more information related to the change.

Approve the change as requested.

Approve the change subject to specified conditions. The change decision is based primarily on the following criteria:

Risk to the project in implementing the change. Risk to the project in not implementing the change.

Impact to the project in implementing the change (time, resources, finance, quality).

Implement Change Request

This process concerns the complete implementation of the change, which includes: Identifying the change schedule (i.e., date for implementation of the change). Testing the change before implementation. Implementing the change.

Reviewing the success of the change implementation. Communicating the success of the change implementation. Closing the change in the change log.

Change Roles

In this process, the roles and responsibilities for all resources (both within and external to the project) involved with the initiation, review, and implementation of changes in the project are defined. For example:

The change requestor initially recognizes a need for change to the project and formally communicates this requirement to the change manager. The change requestor is formally responsible for:

The early identification of a need to make a change to the project.

The formal documentation of that need, through the completion of a change request form.

The submission of the change request form to the change manager for review.

The change manager receives, logs, monitors, and controls the progress of all changes in a project. The change manager is formally responsible for:

Receiving all change requests and logging those requests into the change register.

Categorizing and prioritizing all change requests.

Reviewing all change requests to determine if additional information is required to present the submission to the change review group.

Determining whether a formal change feasibility study is required to complete a change request submission.

Initiating the change feasibility study, through assignment of the change feasibility group.

Monitoring the progress of all change requests to ensure process timeliness.

Escalating all change request issues and risks to the change approval group.

Reporting and communicating all decisions made by the change approval group.

The change feasibility group completes formal feasibility studies for change requests issued by the change manager. The change feasibility group is formally responsible for: