The scope statement turns the charter's high-level scope into something people can agree on and check. It holds:
- Deliverables: what the project hands over (a children's area to code, four self-checkout kiosks).
- Acceptance criteria: how each deliverable will be judged complete (the fire inspector signs the certificate).
- Exclusions: what is out of scope, written down so nobody assumes it is in.
- Assumptions: what you are treating as true without proof (the building has no asbestos).
- Constraints: limits you must work within (the branch must close for no more than four months).
Vague phrases are the enemy of scope. "And anything else the branch needs" turns a fixed project into an open-ended one, and an exclusion that is not written down will be argued about later. Read every line asking: could two people disagree about whether this is done?
A scope statement in five lines.