A project manager is reviewing lessons learned from a previous project and notices that scope creep occurred because stakeholders requested changes after the project moved into the execution phase. Which action should the project manager take in the current project to prevent this issue?
Trap 1: Close the project early if any scope changes are requested.
Closing early is not a standard practice and would prevent delivering planned value.
Trap 2: Involve all stakeholders in the project planning phase to ensure…
While important, this alone does not prevent scope creep without a formal change control process.
Trap 3: Include a detailed list of all deliverables in the project charter…
The project charter is a high-level document; detailed scope is in the scope statement, and a CCB is still needed.
- A
Close the project early if any scope changes are requested.
Why wrong: Closing early is not a standard practice and would prevent delivering planned value.
- B
Involve all stakeholders in the project planning phase to ensure requirements are fully captured.
Why wrong: While important, this alone does not prevent scope creep without a formal change control process.
- C
Include a detailed list of all deliverables in the project charter to avoid ambiguity.
Why wrong: The project charter is a high-level document; detailed scope is in the scope statement, and a CCB is still needed.
- D
Establish a change control board during the planning phase to review and approve any change requests.
A CCB provides a structured process to evaluate changes, preventing unauthorized scope creep.