Project Change Management: Integrated Control and Baseline Protection

PMBOK v8 Definition

Project Change Management is the formal process for managing change requests throughout the project lifecycle. A change request is a formal proposal to modify a document, deliverable, or baseline. Change requests should typically include information on the estimated schedule and cost impacts before they can be approved. If a change request impacts a project baseline, integrated change control measures should follow a formal process to assess and implement those changes. Each documented change request should be approved, deferred, or rejected by a designated person, such as the project sponsor or project manager, as specified in the project management plan or organizational procedures.

Why It Matters for the Exam

Change Management is heavily tested because it is a critical control mechanism in project management. PMI exam questions frequently test your understanding of when formal change control is required (after baseline establishment) and who has authority to approve different types of changes. Expect scenario-based questions where you must determine the correct sequence of change control steps.

Key Points to Remember (for the exam)

• Baseline Trigger: Changes are not formally controlled until baselines are established. Once baselines exist, ALL changes must go through formal integrated change control.

• Required Information: Every change request should include estimated schedule and cost impacts before approval.

• Disposition Options: Each change request must be approved, deferred, or rejected by the designated authority.

• Change Log: The disposition of all change requests is recorded in the change log as a project document update.

• Change Management Plan: This plan establishes the Change Control Board (CCB), documents its authority, and describes how the change control system will be implemented.

• Configuration Management: The configuration management plan specifies which project artifacts are subject to configuration control. Changes to these artifacts require a formal change request.

• Verbal vs. Written: Although changes can be initiated verbally, they must be documented in writing and entered into the change or configuration management system.

Typical PMI Exam Example

A project manager receives a verbal request from a key stakeholder to add a new feature after the scope baseline has been approved. The project manager should first document the request as a formal change request, include estimated schedule and cost impacts, and submit it to the CCB for approval, deferral, or rejection.

PMI Exam Traps

• Trap: Confusing "change request" with "corrective action" Reality: A change request modifies a baseline; corrective action brings future performance back in line with the plan without changing the baseline

• Trap: Thinking the project manager always approves all changes Reality: Authority is defined in the change management plan; the CCB approves baseline-impacting changes, while the project manager may approve changes within defined thresholds

• Trap: Assuming verbal approval is sufficient Reality: Verbal initiation is acceptable, but written documentation and entry into the change management system are mandatory

• Trap: Forgetting that change requests require cost AND schedule impact data Reality: Both estimated schedule and cost impacts are typically required before approval

Important PMI Connections

Quick Review Questions

1. When does formal change control begin in a predictive project approach?

2. What two types of estimated impacts must typically be included in a change request before approval?

3. What are the three possible dispositions for a documented change request?

4. Where is the disposition of all change requests recorded?

5. Who determines the authority to approve, defer, or reject change requests?

PMBOK v8 Reference

Section 2.1.6.8.1 – Predictive Approaches (Change Management) Section 2 – Project Management Performance Domains (Figure 2-11: Assess and Implement Changes flow)