How do you manage scope creep on a project?

Question

Accepted Answer

**Scope creep**, the steady accumulation of "just one more thing", is how on-track projects quietly slip. The fix isn't to say no to everything; it's to make **every addition a visible, explicit trade-off** against time, instead of a silent absorption.

## How to control scope

```text
✓ Define DONE up front — written, agreed scope
✓ Make the cost of every addition VISIBLE ("yes, and that pushes us a week")
✓ Track changes — a changelog of what got added/cut
✓ Protect a core MVP — defend the must-haves fiercely
✓ Use a PARKING LOT — capture good ideas for "later," don't reject them
✓ Escalate trade-offs to whoever owns priority — let them choose
```

## The key move

Don't refuse new requests outright, that makes you the blocker. Instead surface the trade-off: "We can add that. It means either the deadline moves a week or we drop feature X. Which do you want?" Now it's a *business* decision, made by the right person, with eyes open.

## A concrete example

Mid-project, the PM keeps adding "small" tweaks. You start a shared scope-change log. Suddenly everyone sees the original two-week project absorbed three weeks of additions, and the conversation about the deadline becomes obvious and easy.

## Why it matters

Unmanaged scope creep is the silent killer of deadlines, no single change feels big, but they sum to a miss.

Making trade-offs explicit keeps the team protected, the stakeholders informed, and the blame off engineering when scope, not effort, was the cause.