Integrated Change Control
A centralized, structured process to assess, approve or reject, and track change requests so they are handled consistently across the project.
Key Points
- Applies to all proposed changes throughout the project life cycle (predictive, hybrid, or agile).
- Impacts to scope, schedule, cost, quality, resources, and risk are analyzed before any decision.
- Decisions are recorded in a change log; baselines and plans are updated and stakeholders are informed.
- May use a change control board in predictive projects; in agile, governance aligns with backlog management and release planning.
Example
A stakeholder requests an added compliance report mid-project. The team logs the request, analyzes cost, schedule, and risk impacts, and the change control board approves it. The schedule baseline is updated, the backlog and plans are adjusted, and the decision is recorded and communicated through the change log.
PMP Example Question
During execution, multiple stakeholders submit change requests. Which activity best represents Integrated Change Control?
- Documenting lessons learned after project closure.
- Sequencing activities to optimize the critical path.
- Evaluating proposed changes in a single, centralized process, deciding on them, and updating baselines and records.
- Gathering requirements to define project scope.
Correct Answer: C — Centralized evaluation and control of change requests
Explanation: Integrated Change Control focuses on assessing change requests, making decisions, and updating baselines and logs in a coordinated manner.