The scope problem starts before the first line of code
The moving deadline
The project was meant to take eight weeks. It is week fourteen, the feature list has doubled, and every meeting adds "one more small thing".
The most expensive moment in a software project is the one where "while we are at it" gets added to the spec. Each addition sounds small. Together they compound into a scope that is too heavy to carry, and a delivery date that quietly becomes fictional.
Scoping is a constraint exercise, not a wish list. The goal is to find the smallest version that proves the value you are actually trying to prove.
What a good scope document contains
A scope document does not need to be long. It needs to answer six questions clearly.
The problem
What is slow, manual, or costing money today, in one paragraph.
Users and roles
Who uses it, how many, and what each role can do.
Must-haves
The smallest set of features that solves the problem.
Not in scope
What is explicitly left for later, written down.
Integrations
Every system it must connect to, and in which direction.
Success measure
How you will know the first release worked.
Project growing faster than it ships?
Get a free consultationWrite a "not in scope" list alongside the spec
One of the most useful things you can do during a kickoff is document what is explicitly not being built in this phase. It forces the conversation about trade-offs early, when it is cheap. It also gives you something to point to later when a reasonable-sounding request would quietly expand the scope.
A "not in scope" list is not a rejection. It is a backlog. It says: we know this matters, and we are choosing to do it later so we can ship this sooner.
A scoping process that ends in a date you can trust
Day 1
Kickoff
Agree the problem, the users, and the constraints: budget, deadline, systems.
Week 1
Discovery
Walk through the real process with the people who do it.
Week 2
Prioritise
Sort features into must, should, could, and will not (MoSCoW).
Week 2
Estimate and phase
Price and schedule the first release; everything else goes to the backlog.
Key takeaway
Every feature added to this release should push another one out, or move the date. Make that trade visible and scope creep stops being silent.
Frequently Asked Questions
Written by
Sachin Patel
Product & Engineering
