HKSM
Change Request(s)
A change request is the usual mechanism for proposing a modification to the project or product. It remains pending and has no effect until it is formally reviewed and approved.
Key Points
- Used to propose changes to scope, schedule, cost, quality, requirements, deliverables, or project documents.
- Should be documented with justification and impact analysis, then routed through the agreed change control process (e.g., CCB or product governance).
- Status is tracked (submitted, under review, approved, rejected, deferred); only approved requests are implemented and baselines updated.
- In agile environments, approved changes often become prioritized backlog items; governance still applies before altering commitments or baselines.
Example
A stakeholder asks mid-project to add a new compliance report. The project manager logs a change request, the team estimates schedule and cost impact, and the CCB reviews it. After approval, the plan and baselines are updated and the work is scheduled for the next iteration; if rejected, no change is made.
PMP Example Question
Which statement best describes a change request?
- It is implemented immediately to avoid delays.
- It is a formal proposal that must be reviewed and approved before any change is made.
- It is used only when defects are found during testing.
- It is optional documentation for minor scope adjustments.
Correct Answer: B — A formal proposal requiring approval before implementation
Explanation: Change requests are formal proposals and have no effect until approved; they are not immediate, not limited to defects, and are not optional for minor changes unless governance explicitly allows it.
