HKSM

A formal procedure to recognize, log, evaluate, and then authorize or deny proposed changes to project documents, deliverables, and baselines.

Key Points

• Relies on a defined workflow with clear roles (often a change control board) and decision criteria.
• Each change request includes impact analysis across scope, schedule, cost, quality, resources, and risk.
• Only approved changes are implemented and baselines are updated; all decisions are recorded for traceability.
• Works closely with configuration management to maintain version control and auditability throughout the project.

Example

A team member proposes adding a new dashboard. The project manager logs a formal change request, analyzes impacts on scope, schedule, and cost, and presents it to the change control board. After approval, the baseline is updated and the team implements the change; if rejected, the request is documented and not executed.

PMP Example Question

Midway through a project, the sponsor emails a request for an additional reporting feature and asks the team to add it immediately. What should the project manager do next?

1. Log a formal change request and route it through change control for impact analysis and a decision.
2. Implement the change to keep the sponsor satisfied and update documents later.
3. Reject the request because it was not in the original scope.
4. Ask the team for a quick estimate and proceed if the cost is low.

Correct Answer: A - Follow the change control process

Explanation: Change control ensures proposed changes are captured, evaluated, and approved or rejected before any updates to deliverables or baselines occur.