Project Change Management: Integrated Change Control Process
PMBOK v8 Definition
Change management in projects is governed by the Integrated Change Control process, which evaluates and manages all change requests throughout the project. A change request is a formal proposal to modify a document, deliverable, or baseline. The change log is a comprehensive list of all changes submitted during the project, including the current status and disposition of each submitted change. The change management plan, a component of the project management plan, establishes the change control board (CCB), documents its authority, and describes how the change control system will be implemented.
Why It Matters for the Exam
Change management is tested in 30-40% of exam questions across multiple domains, particularly in planning, executing, and monitoring/controlling. Questions frequently test your ability to distinguish between change request types (corrective action, preventive action, defect repair, update) and to identify the correct sequence of the change control process. Expect scenario-based questions where you must determine who approves a change, what document is updated first, and whether a baseline change requires formal integrated change control.
Key Points to Remember (for the exam)
- Four Types of Change Requests: Corrective Action (fixes deviation), Preventive Action (avoids future deviation), Defect Repair (fixes nonconforming product), Update (modifies documents/plans without baseline impact)
- Change Log: Comprehensive list of ALL submitted changes; records disposition (approved, rejected, deferred, more information needed); updated as a project document update
- CCB Authority: The change management plan documents the CCB's authority and how the change control system is implemented; CCB approves/rejects changes that impact baselines
- Baseline Impact Rule: Any change impacting a project baseline MUST follow formal integrated change control measures
- Approval Authority: Designated person (project sponsor, project manager, or CCB) as specified in the project management plan or organizational procedures
- Change Request Content: Must include estimated schedule and cost impacts before approval
- Sponsor Accountability: Project sponsor is accountable for the business case document; project manager keeps success measures aligned across business case, project management plan, project charter, and benefits management plan
Typical PMI Exam Example
A project manager receives a request from a stakeholder to add a new feature to the project deliverable. The feature would extend the schedule by two weeks and increase costs by $15,000. The project manager documents the request, performs an impact analysis, and submits it to the CCB. The CCB reviews the estimated impacts and rejects the change. The project manager records the rejection in the change log.
PMI Exam Traps
-
Trap: Confusing "corrective action" with "defect repair" Reality: Corrective action realigns performance to the plan; defect repair fixes a nonconforming product or component
-
Trap: Thinking the project manager always approves changes Reality: Approval authority depends on the change management plan; baseline changes typically require CCB approval
-
Trap: Assuming all change requests are approved Reality: Change requests can be approved, rejected, deferred, or require more information; all dispositions are recorded
-
Trap: Confusing the change log with the issue log Reality: Change log tracks submitted changes and their disposition; issue log tracks problems, constraints, and concerns
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Business Case | Input to project initiation; sponsor accountability | Sponsor maintains; PM aligns success measures |
| Project Management Plan | Contains change management plan component | Change management plan defines CCB and process |
| Project Charter | Authorizes project; aligned with business case | PM ensures alignment between charter and changes |
| Benefits Management Plan | Tracks realized benefits; affected by changes | Changes may require benefits re-evaluation |
| Risk Register | Impacted by change requests | Changes may introduce new risks or alter existing ones |
Quick Review Questions
- A change request that modifies a project baseline must follow what type of process?
- What document records the disposition of all change requests?
- Who is accountable for the development and maintenance of the business case document?
- What four types of change requests can be submitted during a project?
- What information must a change request typically include before it can be approved?
PMBOK v8 Reference
Section 2 – Project Management Performance Domains, Figure 2-11: Example Flow for Project Changes
Section 4 – (Business documents context) Figure 4-12: Sponsor and Business Documents Relationship to Initiating Actions