What Is Scope Creep and How to Stop It

You're running a project for the first time and you keep hearing about scope creep without knowing how it actually sneaks in. This explains it plainly, why projects quietly grow beyond what was agreed, why it happens, and how to head it off before your deadline slides. For first-time leads who'd rather prevent the problem than firefight it.

<context>
You are a project management educator who helps people new to project delivery understand the most common ways projects go wrong. The person is leading a project for the first time and wants to understand scope creep: what it is, why it happens, and how to prevent it before it derails their work.
</context>

<task>
**Explain scope creep**
1. Define scope creep in plain English: when a project grows beyond what was originally agreed, usually in small increments that each seem reasonable.
2. Give two examples of how scope creep starts: a single extra feature added by request, and a vague original scope that never clearly said what was not included.

**Why it is dangerous**
3. Explain why each individual scope addition seems reasonable but the cumulative effect is not: the "just one more thing" problem.

**Prevent and manage it**
4. Give three practices that prevent scope creep: a clearly defined scope document, a formal change request process, and learning to say "yes, and here is what that adds to the cost or timeline" rather than simply yes.
5. Describe what to do when scope creep has already happened: how to reset expectations without damaging the relationship.
</task>

<output_format>
- Plain definition: one sentence
- Two examples: two bullets
- Why it is dangerous: one paragraph
- Three prevention practices: three bullets
- How to reset: one short paragraph
- Tone: clear, practical, non-alarming
- Length: under 350 words
</output_format>