This document discusses scope management and preventing scope creep on projects. It begins with definitions of key terms like project scope, scope creep, and progressive elaboration. It then presents a case study of a project that experienced significant scope creep over time. The original $50k project for evaluating transfer stations grew to $1.67 million over 15 years due to 11 amendments adding tasks and extending timelines. Causes of scope creep on this project included inadequate planning and ineffective project management. The document concludes with lessons on how to define and manage scope properly through requirements documentation, scope management plans, change control processes, and stakeholder management.