Change Control in PMP: Integrated Change Control

Change control is one of the most tested topics in the PMP Process domain — and one of the most misunderstood. The PMI mindset around change is structured: analyze, document, approve, then implement. This guide covers the full process.

What Is Integrated Change Control?

Integrated change control is the process of reviewing, approving, and managing changes across all project aspects — scope, schedule, cost, quality, risk, and resources — in a coordinated way. "Integrated" means changes are evaluated holistically, not in isolation.

The Change Control Process

Step 1: Identify the Change

A change can come from anywhere — a stakeholder, the team, a risk event, a regulatory update. The PM captures it.

Step 2: Document the Change Request

Create a formal change request that includes:

• Description of the change
• Reason for the change
• Impact analysis (scope, schedule, cost, quality, risk)
• Alternatives considered
• Recommendation

Step 3: Analyze the Impact

This is the critical PMI mindset step. Before approving or rejecting, analyze:

• Scope: Does the change affect deliverables?
• Schedule: Does it extend the timeline?
• Cost: Does it increase the budget?
• Quality: Does it affect quality standards?
• Risk: Does it introduce new risks?
• Resources: Does it require additional team members?

Step 4: Submit to the CCB

The Change Control Board (CCB) — a formally chartered group — reviews and approves, defers, or rejects the change.

Step 5: Update the Plan

If approved, update the affected baselines:

• Scope baseline
• Schedule baseline
• Cost baseline
• Quality plan
• Risk register

Step 6: Communicate

Inform all stakeholders of the approved change and its impacts.

Step 7: Implement and Track

Execute the change and monitor its effects on the project.

The Change Control Board (CCB)

The CCB is typically composed of:

• Project sponsor
• Key stakeholders
• Subject matter experts
• The project manager (facilitator, not decision-maker)

The CCB's role is to evaluate changes objectively and decide based on business value and project impact.

Configuration Management

Related but distinct — configuration management tracks the state of deliverables and documentation:

• Configuration identification
• Configuration status accounting
• Configuration verification and audit

The PMI Mindset for Change

1. Never implement a change without analysis — always assess first
2. Document everything — change requests, analysis, approvals
3. Engage the CCB — don't approve changes unilaterally
4. Update baselines — keep them current
5. Communicate — stakeholders need to know about approved changes

Common Change Control Exam Traps

• Implementing before analyzing — PMI always analyzes first
• Approving without CCB — unless the PM has authority, changes go through the CCB
• Forgetting to update baselines — approved changes update the baseline
• Confusing configuration management with change control — they're related but distinct

Scenario Example

A key stakeholder requests a new feature mid-project. The sponsor is supportive. What should the PM do FIRST?

• A. Implement the feature to satisfy the stakeholder.
• B. Submit the change request to the CCB.
• C. Analyze the impact on scope, schedule, and cost.
• D. Update the project schedule.

Correct: C — analyze first. The PMI mindset requires impact analysis before any action, even if the sponsor is supportive.

Final Thoughts

Change control rewards the PMI mindset: analyze, document, approve, communicate, implement. Memorize the sequence, practice scenarios, and you'll handle change questions with confidence. The key rule: never act before analyzing.