MSPM1-GC4000 Enterprise Project Change Management Plan

This document presents a comprehensive change management plan designed for an enterprise-level project. It begins with an introduction that highlights the importance of change management, particularly in technology-driven projects where updates and market fluctuations necessitate adjustments. The plan defines key concepts such as scope, scheduling, and budget changes, and outlines the roles and responsibilities of the change control board. A detailed change request form is provided, covering various change categories like schedule, cost, scope, and resources, along with sections for describing the change, its rationale, alternatives considered, technical implications, and associated risks. The plan also includes a change control process flow and sections for approvals from the project manager, change control board, and executive sponsor. Furthermore, the document touches upon procurement, quality, risk, work breakdown structure, and budget management, providing a holistic view of project management. The preliminary budget includes cost estimations for different categories, and the document concludes with a detailed analysis of project quality management, outlining a step-by-step approach to identify stakeholders, develop requirements research plans, and create specifications for measurable standards. The plan emphasizes quality assurance and control through various activities and metrics, ensuring the project's success through effective change management and quality control.

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
The Change Management Plan
The Project Title
The Organization Name or Business Unit Name or Department Name
The Project Solution
Authors Name:
Date:
Student Name:
Course Name:
Course ID Number:
Team Name and Number:
Date:
1

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
Introduction and Purpose
Change management is necessary when certain changes are required in a project and they need
to be integrated with the current progress of the project. Change management is required
when the client makes changes in the requirements or when the project requires changes in
order to improve the quality and follow the scope more distinctly. The need for change
management in a tech project arises when there is a new version of a software / hardware is
available or the chosen hardware or software gets outdated. In both cases, the market prices of
the updated versions increase significantly thus requiring change in the project.
The purpose of the change management depends on the nature of changes that are
introduced. If a client requests some changes in requirements, they need to be incorporated
within the project. Again, if the project manager finds that the progress of the project is not
satisfactory or it has gone beyond the limits of the scope, then he can introduce changes in the
project.
Change Management
Change management is required to govern and control the process of implementation of a
change in the project. Any change cannot be just introduced in the project, it requires proper
evaluation, feasibility testing and adjustments to the budget before it can be implemented in
the project. It is the duty of the project manager to develop suitable change management plan
based on the requirements of the project and the proposed changes. For this project, there
may arise the need for changes due to release of new versions of the devices that are selected
for this project. On the other hand, the aim of this project is to only use the best quality of the
technology augmentation devices to satisfy the customers. Hence, change might be required in
the project in order to update the requirements as well as the resource requirements for the
project.
Definitions of Change
 Scope Changes:
 Scheduling Changes:
 Budget Changes:
Change Control Board
Roles and Responsibilities
2

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
3

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
Change Request Form
Project Title:
Organization/Business Unit/Department:
Product/Process:
Date:
Change Requestor: Date:
Change No:
Change Category (Check all that apply):
□ Schedule √Cost □ Scope □ Requirements/Deliverables
□ Testing/Quality √Resources
Does this Change Affect (Check all that apply):
□ Corrective Action □ Preventative Action □ Defect Repair √Updates
□ Other
Describe the Change Being Requested:
The proposed change includes some modifications in the budget as the market prices of certain resources required for
the project have increased and will continue to increase during the execution of the project. Moreover, some new
versions of devices have been released in the market that also have increased prices, thus requiring additional budget.
Describe the Reason for the Change:
The main reason for the change is the increase in the market prices of the resources like iPads and other technological
devices.
Describe all Alternatives Considered:
Other alternatives include use of older versions of the devices in order to cut costs from the project.
Describe any Technical Changes Required to Implement this Change:
There are no technical changes required to implement this change.
4

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
Describe Risks to be Considered for this Change:
The main risk in this case is that the additional budget can result in significant overshoot in the budget that can cause
significant financial losses for the company.
Estimate Resources and Costs Needed to Implement this Change:
The proposed additional cost for this project is $10,000 that will be used to procure most recent versions of the devices
required for the project.
Describe the Implications to Quality:
The additional budget will significantly enhance the quality of the project as the latest versions of the devices will be
purchased.
Disposition:
□ Approve □ Reject √Defer
Justification of Approval, Rejection, or Deferral:
The request needs to be further analyzed and discussed with the board members before it is approved.
5

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
Change Control Process
Process Flow
6

Enterprise Project Management
MSPM1-GC4000
Edward Kleinert
Approvals
Prepared by__________________________________
Project Manager
Approved by__________________________________
Change Control Board
___________________________________
Executive Sponsor
7