Which practice helps prevent scope creep in Mega Goal projects?

• A. Baseline the project only at the end
• B. Change control
• C. Obtain sign-off after completion
• D. Avoid documenting acceptance criteria

Answer: (B)

When you want to prevent scope creep, a formal change control process is essential. Scope creep happens when new work is added without review and approval, so change control creates a gate for any request to change scope, requirements, or deliverables, requiring documentation, impact analysis on schedule and budget, and formal approvals before the work proceeds. This keeps the project aligned with its goals and updated plans. Baselining only at the end is too late to catch changes; signing off after completion doesn't prevent midcourse changes; and avoiding acceptance criteria leaves ambiguity that invites additional requests. By enforcing change control, you ensure every change is intentional and understood in terms of cost, time, and value.