Project scope statement template
A free project scope statement template in Word and Markdown — product scope, deliverables, acceptance criteria, in scope, out of scope, constraints and assumptions, with guidance in every section.
What's inside
- Project and versionProject name, version of this statement, date, and who approved it.
- Product scope descriptionWhat the result is: its features and characteristics, in plain words.
- DeliverablesEach thing the project hands over, including documents and training, not just the main product.
- Acceptance criteriaFor each deliverable, the test or condition that makes it accepted, and who accepts it.
- In scopeThe work the project will do. Be specific enough that two people would read it the same way.
- Out of scope (exclusions)What the project will not do, even if someone might assume it will. This section prevents most scope arguments.
- ConstraintsFixed limits: dates, budget, regulations, sites, technology.
- AssumptionsWhat you are treating as true without proof. Each one also goes in the assumption log.
- ApprovalName, role, signature and date of the sponsor and the customer.
What a scope statement is
The scope statement says what the project will deliver and, just as important, what it won't. It takes the high-level scope in the charter and makes it precise enough to plan against, estimate and accept. Together with the WBS and its dictionary, it forms the scope baseline.
When to use it
After the charter is approved and the requirements are gathered, before the WBS is built. Update it only through change control: once it is approved, a change to scope is a change request.
How to fill it in
- Describe the product in plain words: what it is and what it does.
- List every deliverable, including the ones that aren't the main product: manuals, training, handover documents, warranties.
- Give each deliverable an acceptance criterion: a test someone can pass or fail, and who decides.
- Write the exclusions. Most scope disputes come from something one side assumed was included. If it could be assumed, write it down as out of scope.
- Record constraints and assumptions, and copy each assumption to the assumption log so someone checks it.
The example at the end is from the Coral Ridge Resort sample project.
Common mistakes
- Exclusions left blank. "Everything else is out" protects nobody.
- Acceptance criteria nobody can test, such as "high quality" or "user-friendly".
- Deliverables that are activities. "Install the chillers" is work; "chilled-water system, commissioned" is a deliverable.
See it used on a real project: Pr2 · Develop and manage project scope