Perform Integrated Change Control

Perform Integrated Change Control

Introduction: Why This Matters

Change is inevitable in projects. New requirements emerge, risks materialize, and stakeholders refine expectations. Without structured control, these changes can lead to scope creep, missed deadlines, and blown budgets. The Perform Integrated Change Control process ensures all change requests are evaluated, approved, or rejected systematically, and only authorized changes are implemented (Project Management Institute, 2021).

On the PMP exam, this process is heavily tested through situational questions about how to handle change requests, the role of the Change Control Board (CCB), and when to update baselines. In practice, integrated change control protects project integrity, aligns changes with strategic goals, and maintains stakeholder trust.

Purpose and Objectives

Primary Purpose: To review, approve, or reject change requests, and to manage changes to project documents, deliverables, and baselines.

Key Objectives:

• Ensure changes are considered in a structured, consistent way.
• Evaluate impact of changes on scope, schedule, cost, quality, resources, and risks.
• Facilitate decision making through the Change Control Board.
• Document decisions and update project baselines where approved.
• Maintain alignment with organizational and project objectives.

Overview

Perform Integrated Change Control is the centralized decision point for all requested changes. It connects what stakeholders want to change with how the project will be impacted and ensures that only evaluated, approved changes become part of the project.

• Centralized control: All change requests flow through a single, formal process.
• Impact first: Changes are analyzed before any implementation happens.
• Baseline protection: Scope, schedule, and cost baselines are updated only when changes are approved.
• Governance: The CCB acts as the formal authority for significant changes.

Characteristics

• Formal and documented: Every change request is logged, tracked, and stored in the change log.
• Integrated: Evaluates effects across all constraints, not just one or two.
• Decision driven: Uses defined authority levels and decision rules (CCB, sponsor, PM).
• Traceable: Decisions and rationales are documented and communicated to stakeholders.

Inputs, Tools & Techniques, Outputs (ITTOs)

Inputs

• Project management plan (baselines and subsidiary plans).
• Work performance reports.
• Change requests.
• Enterprise environmental factors (approval processes, authority levels).
• Organizational process assets (change control procedures, templates).

Tools & Techniques

• Expert judgment: Functional managers, subject matter experts, PMO.
• Change control tools: Software to log and track change requests.
• Data analysis: Impact analysis, cost benefit analysis, alternatives analysis.
• Decision making: Voting, autocratic decisions, consensus, majority rule.
• Meetings: Change Control Board sessions, impact review discussions.

Outputs

• Approved or rejected change requests.
• Updates to project management plan (scope, schedule, cost baselines).
• Project document updates (change log, requirements, risk register).

The Change Control Process

1. Submit Change Request

• Can be initiated by any stakeholder.
• Documented formally (scope change, defect repair, preventive action, corrective action).

2. Log and Track

• Entered into the change log for transparency.

3. Impact Analysis

• Evaluate effects on all project constraints (scope, schedule, cost, quality, risk, resources, stakeholder engagement).

4. Decision Making

• The Change Control Board or authorized entity approves, rejects, or defers.

5. Communicate Outcome

• Decision communicated to all stakeholders.

6. Update Plans and Baselines

• If approved, update project documents, management plans, and baselines.

7. Implement Approved Changes

• Passed to Direct and Manage Project Work for execution.

Change Control Board (CCB)

• A formally chartered group responsible for reviewing change requests.
• Composition may include sponsor, project manager, functional managers, and key stakeholders.
• Authority and decision rules are defined in the change management plan.

Practical Example: Public Transportation System Upgrade

Context: A city is upgrading its subway system.

Change request: A stakeholder proposes adding new passenger information displays not originally in scope.

Perform Integrated Change Control activities:

• Log: The request is recorded in the change log.
• Impact analysis: Additional cost of $500,000 and schedule delay of three weeks. Benefits include improved passenger satisfaction and compliance with accessibility regulations.
• CCB decision: Approves the change due to regulatory requirement.
• Updates: Cost and schedule baselines updated, procurement plan revised.
• Implementation: Approved change executed in Direct and Manage Project Work.

Outcome: The project accommodates the change without uncontrolled scope creep, and the system meets new accessibility standards.

Common Pitfalls

Implementing changes informally

• Pitfall: Teams act on verbal requests.
• Prevention: Require all changes to go through formal control.

Incomplete impact analysis

• Pitfall: Considering only cost or schedule, ignoring quality or risk.
• Prevention: Evaluate changes across all constraints.

Poor communication of decisions

• Pitfall: Stakeholders unaware of why a change was rejected or approved.
• Prevention: Document and share rationale transparently.

Weak documentation

• Pitfall: Change requests not tracked, leading to confusion and rework.
• Prevention: Maintain an updated, accessible change log.

Quick Recap Table

Key Takeaways

• Perform Integrated Change Control is the structured process for managing changes to the project.
• The Change Control Board provides governance and ensures alignment with strategy and constraints.
• Only approved change requests are implemented and reflected in updated baselines.
• On the PMP exam, correct answers emphasize logging, analyzing, deciding, then implementing.
• In practice, strong change control prevents chaos, scope creep, and misalignment with project goals.

Next Step

With Perform Integrated Change Control covered, the next process is Validate Scope, where deliverables are formally accepted by stakeholders.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.