Project Analysis Change: Integrated Change Control Process

PMBOK v8 Definition

The Assess and Implement Changes process involves reviewing all change requests, approving or rejecting changes, and managing changes to deliverables, project documents, and the project management plan. This process is performed throughout the project and belongs to the Project Performance Domain of project management. The decision on a change request results in one of three outcomes: Approved, Rejected, or Deferred—where a deferred change is not added to the backlog, or an existing change is removed from the backlog, meaning it is rejected.

Why It Matters for the Exam

Project Analysis Change questions appear frequently in PMI exams, particularly in scenarios involving scope creep, baseline management, and stakeholder requests. You will encounter these questions in situational judgment items where you must determine the correct sequence of change control activities or identify the appropriate outcome of a change request.

Key Points to Remember (for the exam)

• Three Possible Decisions: Every change request results in exactly one outcome: Approved, Rejected, or Deferred (deferred = rejected for the current backlog).
• Main Input: The primary input is the Change Request itself, along with the Project Management Plan (all components, especially the Change Management Plan and Configuration Management Plan).
• Main Output: The key output is the Decision (Approved, Rejected, or Deferred) documented in the Change Log.
• Key Tool: Data Analysis techniques, including Document Analysis, Regression Analysis, Trend Analysis, and Variance Analysis.
• Common Confusion: Deferred changes are often mistaken as "pending approval"—in PMBOK v8, choosing not to add a change to the backlog means it is rejected.
• Impact Analysis Requirement: Before a decision, an Impact Analysis must be performed across Scope, Finance, Schedule, Resources, Stakeholders, and Risk.
• CCB Involvement: A Change Control Board (CCB) or Project Board may be involved in the decision process.

Typical PMI Exam Example

A project manager receives a change request from a key stakeholder to add a new feature. After analyzing the impact on the schedule and cost baselines, the change control board reviews the request. The CCB determines the change would cause a 20% schedule delay and rejects the request. The project manager updates the Change Log with the decision and informs the stakeholder.

PMI Exam Traps

• Trap: Thinking "Deferred" means the change is still under consideration. Reality: In PMBOK v8, a deferred change is rejected—it is not added to the backlog or is removed from the existing backlog.

• Trap: Confusing "Corrective Action" with "Preventive Action." Reality: Corrective Action fixes an existing deviation; Preventive Action avoids a potential future deviation. Both are types of change requests.

• Trap: Believing all change requests go to a CCB. Reality: The project manager can approve some changes within their authority (as defined in the Change Management Plan), while only certain changes require CCB approval.

• Trap: Forgetting that the Project Management Plan is an input to Assess and Implement Changes. Reality: All components of the PM plan (Scope Baseline, Schedule Baseline, Cost Baseline, Change Management Plan, Configuration Management Plan) are inputs.

Important PMI Connections

Quick Review Questions

1. What are the three possible decisions for a change request according to PMBOK v8?
2. If a change request is deferred, is it considered approved, rejected, or pending?
3. Name four types of data analysis tools used in the Assess and Implement Changes process.
4. Which document records the decision of a change request?
5. What is the difference between Corrective Action and Preventive Action?

PMBOK v8 Reference

Section 2 – Project Management Performance Domains (specifically Figure 2-11: Example Flow for Project Changes, and the Assess and Implement Changes process description)