Stop 07 · Agile, Execution & DeliveryTopics · 10/12

Managing Scope Creep

In short

No project explodes from one big change. It grows from twenty small "can we just also…" requests. Spotting them early is a core PM skill.

Recognizing and pushing back on small, seemingly-reasonable additions that quietly balloon a project's timeline — usually solved by explicitly protecting the original scope, not by working faster.

The purple blob holds a very long paper scroll unrolling across the floor.

Think of it like this

The wedding guest list

It starts with 200 guests. Then Mama adds his office friends, someone adds the old neighbours, and "just five more" happens ten times. Suddenly it's 450 and the hall, food and budget are all wrong. Software scope grows the same way.

Watch it happen

How a 4-week project became 7

Core: 4 wk

+ filters

+ export

+ dark mode

+ admin view

1/5The plan: four weeks for the core feature. Everyone agreed.

The big ideas

What you need to know

Write scope down

An explicit in-scope and out-of-scope list gives you something to point to.

Trade, don't add

New request? Ask what comes out. Scope, time and people are linked.

Park it for later

"Great idea, it's on the list for version 2" keeps goodwill without derailing.

Make changes visible

Log every change and its cost in days so stakeholders see the total.

Save yourself the pain

Common mistakes

Oops

Saying yes to small requests to keep people happy.

Do this instead

Small yeses add up. Show the trade-off each time, even for tiny ones.

Oops

Refusing every change on principle.

Do this instead

Some changes are worth it. Accept them openly with a new date or a dropped item.

Your mission

Practise the trade-off reply

~15 min

Quick check

Midway through a fixed-date project, a stakeholder asks for one more feature. What's the best first response?

Go deeper

1Recall a project (yours or observed) that suffered from scope creep and diagnose why.
2Practice the phrase 'let's ship this first, then evaluate that as a fast-follow'.
3Learn to write explicit 'out of scope' sections in specs to prevent this upfront.