Project Scope
Name variants
- English
- Project Scope
- Katakana
- スコープ / プロジェクト
- Kanji
- 範囲
Quality / Updated / COI
- Quality
- Reviewed
- Updated
- Source
- Citations & Trust
- COI
- none
TL;DR
Project scope defines the boundaries of work, including deliverables, exclusions, and acceptance criteria.
Definition
Scope describes what the project will and will not deliver, along with assumptions and constraints. It provides the baseline for planning, estimating, and controlling changes. Clear scope statements reduce misalignment by making tradeoffs explicit and linking outcomes to measurable acceptance criteria.
Decision impact
- It determines which work is included and which requests must be deferred.
- It influences cost and schedule estimates by setting boundaries.
- It provides a standard for accepting or rejecting change requests.
Key takeaways
- Define deliverables and exclusions in plain language.
- Attach acceptance criteria so completion can be verified.
- Review scope with stakeholders early to surface conflicts.
- Use scope to control changes and protect priorities.
- Document assumptions to avoid hidden expansion later.
Misconceptions
- Scope is not a wish list; it is an agreed boundary of work.
- A vague scope does not create flexibility; it creates conflict.
- Scope can change, but only through explicit decisions.
Worked example
A mobile app project defines scope as redesigning the onboarding flow and analytics tracking, explicitly excluding a payment redesign. Acceptance criteria include completion rate and data accuracy. When a stakeholder asks for new payment screens, the team evaluates the request against scope and schedules it for a later phase. This prevents unplanned expansion and keeps delivery on time.
Citations & Trust
- Project Management (Open Textbook Library)