Project Change Request Management and Integrated Change Control

PMBOK v8 Definition

Change requests are formal proposals to modify any project management plan component, project document, or project baseline. Such changes can be proposed by any stakeholder and may occur at any point in the project life cycle. The degree of project change request management applied depends on the scope of the project, its complexity, the contract requirements, and the development approach being used. This process falls under the Assess and Implement Changes performance domain (Section 2 – Project Management Performance Domains).

Why It Matters for the Exam

Change management is one of the most frequently tested topics on the PMI exam, appearing in situational questions where you must determine the correct sequence of change handling. Expect questions testing your understanding of who approves what, when baselines are impacted, and which documents are updated. This concept appears in both process-based and scenario-based questions across all knowledge areas.

Key Points to Remember (for the exam)

• Main Inputs: Project management plan (change management plan, configuration management plan, scope baseline, schedule baseline, cost baseline) + project documents (basis of estimates, change log, requirements traceability matrix, risk report) + work performance reports + change requests
• Main Outputs: Approved, rejected, or deferred change requests + project management plan updates + project document updates
• Key Tool: Integrated Change Control (formal process to assess and implement changes impacting baselines)
• Common Confusion: Corrective action vs. preventive action vs. defect repair
  • Corrective Action: Fixes a problem that has already occurred
  • Preventive Action: Prevents a potential future problem
  • Defect Repair: Fixes a nonconforming product
• Approval Authority: Designated person (project sponsor or project manager) as specified in the project management plan or organizational procedures
• CCB Involvement: Change control board (CCB) or project board may be involved when applicable
• Baseline Impact: If a change request impacts a project baseline, integrated change control measures must follow a formal process

Typical PMI Exam Example

During project execution, a key stakeholder requests adding a new feature to the product. The project manager determines this will impact the scope baseline and schedule baseline. What should the project manager do FIRST? Answer: Submit a formal change request and initiate integrated change control to assess impacts on scope, schedule, cost, resources, stakeholders, and risk before approval.

PMI Exam Traps

• Trap: Confusing change requests with issue logs
  • Reality: Change requests are formal proposals for modification; issue logs track problems that have occurred
• Trap: Thinking the project manager always approves changes
  • Reality: Approval authority depends on the project management plan or organizational procedures; a CCB may be required for baseline changes
• Trap: Assuming all changes require the same level of rigor
  • Reality: The degree of change management depends on scope, complexity, contract requirements, and development approach
• Trap: Believing only the project manager can propose changes
  • Reality: Any stakeholder can propose a change at any point in the project life cycle

Important PMI Connections

Quick Review Questions

1. A change request is submitted that impacts the cost baseline. Who must approve this change according to PMBOK v8?
2. What are the three possible dispositions for a documented change request?
3. List five inputs to the Assess and Implement Changes process.
4. What is the difference between a corrective action and a preventive action?
5. At what point in the project life cycle can a stakeholder propose a change?

PMBOK v8 Reference

Section 2 – Project Management Performance Domains (Assess and Implement Changes) Section 4 – Inputs and Outputs (Project Document Updates)