How Healthy Is Your Scope Statement? A Self-Assessment for New PMs at Scale-Ups
A detective self-assessment for individual contributors at scale-ups — to evaluate whether your existing scope statement will hold up against expansion, before expansion has started.
Ten questions that tell you whether your scope statement will survive month four
A scope statement that scores below seven is not a scope statement. It's a wishlist that hasn't been challenged yet.
Individual contributors at scale-ups often inherit scope statements written by someone else — a sponsor, a consultant, a sales engineer — and have to figure out whether the statement is going to hold up under execution pressure. The expansion pattern usually starts in month two or three, and by then it's too late to retrofit the scope statement. The detective work has to happen earlier.
This self-assessment is ten yes/no questions about your existing scope statement. Score honestly. The total tells you whether the document is doing its job — or whether you should be pushing for revision now, while it's still cheap.
Ten questions, 1 point per yes
0 / 10- Does the scope statement lead with a measurable customer or business outcome?
- Does it name a specific customer segment or user behavior, not a generic audience?
- Does it have an exclusions section that's specific to this project, not generic hypotheticals?
- Are exclusions signed separately from inclusions?
- Does it list every external dependency by name and date?
- Does it name a single individual responsible for scope-change decisions?
- Does it define what counts as a scope change vs an interpretation of existing scope?
- Does it include operational or run-state scope, not just build-state?
- Does it include re-evaluation triggers — events that would force a scope statement update?
- Has it been re-read by the team in the last 30 days?
How to read your score
8–10: Healthy scope statement. It's doing the job. Continue using it actively. Re-read quarterly.
5–7: Average scope statement. Most projects sit here. Identify which questions you scored no on, prioritize the ones that protect against expansion (3, 4, 5, 6, 7), and address one per week until the score is 8 or higher.
Below 5: The scope statement isn't doing the job. This is more common than people admit. The corrective is not to write a new scope statement — that triggers political resistance — but to add specific sections to the existing one. Each addition can be made incrementally with sponsor sign-off.
What each question diagnoses
The ten questions cluster into three groups.
Outcome and audience cluster (questions 1, 2). These check whether the scope statement is anchored in something specific enough to evaluate scope additions against. If both are no, every scope addition feels reasonable because there's no reference point.
Exclusions and authority cluster (questions 3, 4, 5, 6, 7). These are the protective sections — the ones that actually push back on expansion when stakeholders request additions. These are also the most often skipped. A project that scores all yes on this cluster will hold up against expansion almost regardless of what else is true. A project that scores all no on this cluster will expand silently no matter how well-intentioned the team is.
Lifecycle cluster (questions 8, 9, 10). These check whether the scope statement is treated as a living artifact or a one-time deliverable. Failures here are usually cultural — the team filed the scope statement after signing and never returned to it. The corrective is process: scheduled re-reads, defined re-evaluation triggers, explicit operational scope. Each is a small process addition; together they convert the scope statement from a static document into an active tool.
Acting on the assessment
0 / 5- Identify your lowest-scoring cluster and pick one corrective action this week
- Re-run the assessment monthly. The trend matters more than the snapshot
- Share the score with the project sponsor only if action is needed; otherwise keep it as your own working tool
- If the score drops over time, that's a signal the scope is being expanded faster than the document is being updated
- Re-baseline after major project changes — sponsor change, scope reset, vendor switch — don't carry forward the old score
The assessment is a detective tool, not a fix in itself. Its value is converting a vague feeling that 'something is off with the scope statement' into specific evidence you can act on and bring to sponsor conversations. A score of three on the exclusions cluster is concrete; 'I'm worried about scope creep' is dismissible.
For the specific mistakes that the questions are designed to catch, see seven scope statement mistakes on enterprise software and the campaign equivalent. For the broader executive view, see what scope statements actually do.