Scope Statement
DE: Scope-Beschreibung
A description of the project scope, deliverables, assumptions, and exclusions.
Detailed Explanation
The scope statement describes the project scope, major deliverables, assumptions, and constraints. It documents the entire scope including both project scope (the work to be done) and product scope (the features and functions of the deliverables).
Critically, the scope statement also defines what is excluded from the project. Exclusions are just as important as inclusions — they prevent misunderstandings about project boundaries. A common failure is omitting exclusions, leaving stakeholders to assume everything is included.
The scope statement is the basis for the WBS and serves as a reference throughout the project for scope-related decisions. When questions arise about whether something is 'in scope,' the scope statement is the authoritative source.
Key Points
- Describes project scope, deliverables, and product scope
- Documents assumptions, constraints, and exclusions
- Exclusions are as important as inclusions
- Basis for creating the WBS
- Authoritative reference for scope decisions
- Updated through formal change control
Practical Example
Website redesign scope statement: Included — redesign of 10 pages, mobile responsive, SEO optimization, CMS integration. Excluded — e-commerce functionality, mobile app, content creation (client provides), ongoing maintenance. Assumptions — client provides brand guidelines by week 2, hosting environment is ready. This clarity prevents 90% of scope disputes.
Tips for Learning and Applying
Always include an exclusions section — what is NOT in scope
Document assumptions explicitly — they are risks if proven wrong
Get formal stakeholder sign-off on the scope statement
Reference the scope statement whenever scope questions arise
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.