Defining Scope

Why scope comes first

A schedule is a statement about how long the work will take. Without an agreed definition of what the work is, the schedule is a guess about an unknown quantity — which is why projects with poorly defined scope overrun regardless of how carefully the schedule was constructed.

What a scope statement contains

• Objectives — what the project is for, and the success criteria.
• Deliverables — the tangible things that will be produced, described specifically enough to be recognisable when complete.
• Acceptance criteria — how each deliverable will be judged complete and acceptable, and by whom.
• Exclusions — what is explicitly not included. This section prevents more disputes than any other and is routinely omitted.
• Assumptions — what is taken to be true. Every assumption is a risk.
• Constraints — fixed dates, budget limits, mandated technology, regulatory requirements.
• Dependencies on other projects or external parties.

Requirements

Deliverables are described by requirements — what the result must do and what characteristics it must have. Good requirements are specific, measurable, achievable, relevant and testable. The test of a requirement is whether two competent people would agree on whether it has been met.

Requirements are gathered from the people who will use the result, not only from those who commissioned it, and they conflict. Reconciling those conflicts is a project task, not something to be discovered during acceptance.

Prioritisation

Not all requirements are equal. Classifying them — must have, should have, could have, will not have this time — is essential because it defines what can be traded when time or budget becomes tight. A project with no prioritisation has nothing to trade and must either overrun or fail.

Two rules make it work: the must-have set should be genuinely minimal, and the "will not have" list should be written down, because it records decisions that would otherwise be re-litigated repeatedly.

Scope creep and gold plating

Scope creep is uncontrolled expansion through accumulated small additions, each reasonable in isolation. It is prevented by a change control process that makes the cumulative impact visible, not by refusing all changes.

Gold plating is the team adding unrequested improvements. It consumes budget, introduces risk and delivers no benefit the customer asked for. It is usually well-intentioned and should still be stopped.