Preventing Scope Creep

C.

Scope creep refers to the tendency for a project's scope to expand beyond its original requirements, often due to requests for changes or additional features. This can result in increased costs, delays, and other issues, so it is important for project managers to take steps to prevent it.

In this scenario, the CEO has approached a project team member to request a project change. To prevent scope creep, the BEST step for the project manager to take would be to submit the request to the change control (CC) board.

The change control board is a group of stakeholders who are responsible for reviewing and approving or denying changes to the project scope. By submitting the CEO's request to the CC board, the project manager ensures that the request is reviewed and evaluated by a group of experts who can assess the potential impact of the change on the project's timeline, budget, and overall success.

Option A, denying the CEO's request, may not be the best approach, as it could damage the relationship between the project team and the CEO. Option B, implementing the project change without proper evaluation, can lead to scope creep, which can cause issues for the project. Option D, asking the CEO to follow the communications plan, is a good idea, but it may not prevent scope creep if the change is not evaluated by the CC board.

In conclusion, the best step for the project manager to prevent scope creep in this scenario is to submit the CEO's request to the CC board for review and approval or denial.