Change Management Plan

A section of the project management plan that sets up the change control board, defines the scope of its decision-making authority, and explains how the change control system will be carried out.

Key Points

  • Establishes the change control board (CCB), its membership, roles, and decision rules.
  • Defines how change requests are submitted, analyzed, approved or rejected, and recorded.
  • Specifies authority limits, escalation thresholds, response timelines, and communication steps.
  • Describes tools, artifacts, and interfaces with the change log and configuration management.

Example

On a hospital IT upgrade, the plan names the CIO, project manager, and clinical lead as the CCB, sets a 5-business-day decision SLA, requires impact analysis on scope, schedule, cost, quality, and risk, and mandates that approved changes are baselined and communicated via a weekly change bulletin.

PMP Example Question

Which document defines who sits on the change control board, how much authority they have, and the steps for evaluating and implementing change requests?

  1. Issue Log
  2. Change Log
  3. Configuration Management Plan
  4. Change Management Plan

Correct Answer: D — Change Management Plan

Explanation: The change management plan establishes the CCB, its authority, and the procedures for processing and implementing changes.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course