PK0-004 · Question #316
A Chief Executive Officer (CEO) has approached a project team member to request a project change. Which of the following would be the BEST step for the project manager to take to prevent scope creep?
The correct answer is C. Submit the request to the CCB. To prevent scope creep, all change requests must flow through the formal Change Control Board (CCB) process regardless of who is requesting the change.
Question
A Chief Executive Officer (CEO) has approached a project team member to request a project change. Which of the following would be the BEST step for the project manager to take to prevent scope creep?
Options
- ADeny the CEO's request.
- BImplement the project change.
- CSubmit the request to the CCB.
- DAsk the CEO to follow the communications plan.
How the community answered
(49 responses)- A14% (7)
- B4% (2)
- C76% (37)
- D6% (3)
Why each option
To prevent scope creep, all change requests must flow through the formal Change Control Board (CCB) process regardless of who is requesting the change.
Flatly denying a CEO's request without a formal review process is inappropriate and bypasses the change governance structure.
Implementing the change without CCB approval is the definition of scope creep, as it adds work outside the approved scope baseline.
Submitting the request to the CCB ensures that even high-authority stakeholders like a CEO must follow the formal change control process. The CCB evaluates the impact on scope, schedule, cost, and quality before approving or rejecting the change. Bypassing this process for any requester, regardless of seniority, is a primary cause of scope creep.
The communications plan defines how information is shared among stakeholders and does not govern how change requests are submitted or controlled.
Concept tested: Change control board process to prevent scope creep
Source: https://www.pmi.org/pmbok-guide-standards
Topics
Community Discussion
No community discussion yet for this question.