CompTIA Project+ (PK0-005)Project Life Cycle PhasesMedium
During project execution, a team member submits a request to add a new feature that was not part of the original scope. Per proper project governance, who should evaluate and approve or reject this request before any work begins on it?
- AThe end user requesting the feature
- BThe functional manager of the requester
- CThe change control board
- DThe project sponsor only, informally
Show answer & explanationAnswer & explanation
Correct answer: C. The change control board
Formal change requests should be routed through the change control board (CCB), which assesses the impact on scope, schedule, cost, and quality before approving or rejecting the change. Allowing individuals or informal approvals to authorize changes bypasses governance and risks scope creep.
Why the other options are wrong
- A. The requester cannot unilaterally approve their own change.
- B. A functional manager typically has no authority over project scope decisions.
- D. Informal sponsor approval bypasses the formal governance process.
Change Control Board (CCB)
A formally chartered group responsible for reviewing, approving, deferring, or rejecting changes to project baselines during monitoring and control.
- Evaluates impact on scope, schedule, cost, and quality
- Approved changes update the relevant baseline
- Bypassing the CCB is a common cause of scope creep
Memory trick: 'Perform, Vary, Change, Risk, Quality' - the five checks of control.