You're mid-way through a high-priority CE rollout. The education team asks to add another topic. What is the BEST next step?

You're mid-way through a high-priority CE rollout. The education team asks to add another topic. What is the BEST next step?

• A. Approve the request
• B. Update project dashboard
• C. Refer to the scope of document
• D. Notify leadership of the change request

Answer: (C)

During a high-priority rollout, any request to add work must be checked against the approved boundaries of the project. The scope document sets those boundaries by defining which topics, deliverables, timelines, and constraints have already been approved. Referencing it first ensures the team knows whether the requested topic is within the approved scope or if it would be a scope change. This step also signals whether formal change-control and impact assessment are required before proceeding, which helps protect the rollout timeline and resource plan. If the topic is within scope and feasible, you can move forward with the appropriate change-management steps to incorporate it. If it isn’t, you escalate and manage the change through the established process, potentially re-baselining timelines or reallocating resources. Approving a new topic without this review risks scope creep and misalignment; updating the dashboard or notifying leadership without evaluating impact can mislead stakeholders or derail the plan.

During a high-priority rollout, any request to add work must be checked against the approved boundaries of the project. The scope document sets those boundaries by defining which topics, deliverables, timelines, and constraints have already been approved. Referencing it first ensures the team knows whether the requested topic is within the approved scope or if it would be a scope change. This step also signals whether formal change-control and impact assessment are required before proceeding, which helps protect the rollout timeline and resource plan.

If the topic is within scope and feasible, you can move forward with the appropriate change-management steps to incorporate it. If it isn’t, you escalate and manage the change through the established process, potentially re-baselining timelines or reallocating resources. Approving a new topic without this review risks scope creep and misalignment; updating the dashboard or notifying leadership without evaluating impact can mislead stakeholders or derail the plan.