Project scope defines what a project will accomplish and the boundaries that keep delivery focused. It records goals, requirements, acceptance criteria, assumptions, constraints, risks, and exclusions. section 10.1.2
Scope becomes useful after stakeholders align on priorities, resources, budget, competing demands, and the project’s value. Clear documentation helps teams understand what delivery includes—and what it does not. section 10.1.2
Define scope by asking and recording:
- What problem, customer need, or business goal does the project address? section 10.1.2
- Which product requirements, functional requirements, nonfunctional requirements, and acceptance criteria must be satisfied? section 10.1.2
- What is in scope, what is out of scope, and which assumptions, constraints, risks, timeline, and budget apply? section 10.1.2
Example: Project Accessible
Stakeholders prioritize an accessibility project as a must-have after discussing business value and return on investment. Scope definition then clarifies its requirements, boundaries, risks, and success measures. section 10.1.2








