Which practice is most directly associated with preventing scope creep?

• A. Frequent scope expansion without review
• B. Change control
• C. Ignoring change requests
• D. Minimal stakeholder involvement

Answer: (B)

Preventing scope creep hinges on having a disciplined process to evaluate and approve changes to the project scope before they are implemented. Change control is exactly that: a formal process where any proposed change is documented, its impact on time, cost, and quality analyzed, and only after review and approval by the right stakeholders is it incorporated into the project. This keeps the scope stable and aligned with objectives, because it requires deliberate decision-making rather than letting changes be introduced informally. The other options undermine control: expanding scope without review invites uncontrolled growth; ignoring change requests hides problems and stalls progress; minimal stakeholder involvement reduces buy-in and clarity, making it harder to manage what should or shouldn’t be included.