🚧 Scope Creep Management
Preventing and controlling unplanned scope expansion.
What is scope creep?
Gradual, uncontrolled growth of project scope without corresponding adjustments to time, budget, or resources.
Warning signs
- "Can we just add one more thing?"
- Requirements changing after sign-off without formal process
- No written scope document
- Stakeholders adding requests directly to the team
- Timeline stays the same while scope grows
Prevention strategies
- Document scope clearly at project start with explicit boundaries
- Change request process — Every addition goes through formal review
- Impact analysis — For each change: what does it cost in time, effort, risk?
- Trade-off conversations — "We can add X, but we need to drop Y or extend the deadline"
- Scope freeze — Define a cut-off date after which no new features are accepted
Change request template
| Field | Content |
|---|---|
| Requested by | ... |
| Description | What is the change? |
| Justification | Why is it needed? |
| Impact on timeline | ... |
| Impact on resources | ... |
| Decision | Approved / Rejected / Deferred |
| Approved by | ... |
Saying no constructively
- "That's a great idea — let's add it to the backlog for the next phase."
- "We can do that, but it means pushing the deadline by X days. Is that acceptable?"
- "Let's evaluate the trade-off: what should we deprioritize to make room?"