Purpose of The Change Management Plan
The Change Management Plan documents and tacks the necessary information required to effectively manage project change from project inception to delivery.
The Change Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan.
Change management Process
The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines.
Change Request Process Flow Requirements
Step |
Description |
Generate CR |
A submitter sends a change request into our Support Help Desk |
Evaluate CR |
Project personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested change |
Authorize / Reject |
Approval to move forward with incorporating the suggested change into the project |
Implement |
If approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders including additional costs if required |
Change Request Should include the following
Element |
Description |
Date |
The date the CR was created |
Title |
A brief description of the change request |
Description |
Description of the desired change, the impact, or benefits of a change should also be described |
Submitter |
Name of the person completing the CR Form and who can answer questions regarding the suggested change |
Phone |
Phone number of the submitter |
|
Email of the submitter |
Product |
The product that the suggested change is for (Moodle / Mahara etc) |
Version |
The product version that the suggested change is for |
Priority |
See our standard Priority Levels. |