Scope and Quality · tool 6 of 9
Scope Statement
Scope Statement: draws the line between what’s in the project and what isn’t.
Best for: After the charter · Time: 2–3 hours
Domain: Scope · Focus area: Planning
How it works
The scope statement describes the deliverables, acceptance criteria, exclusions, assumptions and constraints. Exclusions usually prevent more arguments than anything else on the page.
- State what’s out as clearly as what’s in.
- Write acceptance criteria for each deliverable.
- List assumptions, so that they can be challenged.
How to apply it
- Start from the charter.
- List deliverables and how each will be accepted.
- Add an explicit “not included” section.
- Have the sponsor approve it.
In practice
Included: French and Dutch sites. Not included: German site, mobile app, migrating archives older than 2020.
Pro tip
The most useful sentence in any scope is one that starts “This project will not…”.
Use it
- Playbook: Scope keeps growing
Quick check
Why write exclusions?
Sources
- PMBOK® Guide, 8th edition, and The Standard for Project Management (PMI, 2025)
Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made