HKSM
Define Scope
The work to produce a thorough, specific definition of the project scope and the product it will deliver.
Key Points
- Transforms gathered requirements into a clear scope statement with deliverables, boundaries, and acceptance criteria.
- States what is excluded to limit scope creep and manage stakeholder expectations.
- Establishes the basis for the WBS, cost and schedule estimates, and quality planning.
- Requires close stakeholder collaboration and iterative refinement until agreement is reached.
Example
On a new mobile app project, the team defines scope by documenting the targeted user personas, prioritized features for the first release (login, profile, search), nonfunctional needs (response time under 2 seconds), explicit exclusions (no tablet support in version 1), and acceptance criteria for each feature. This agreed description becomes the foundation for building the WBS and planning the schedule and budget.
PMP Example Question
After completing Collect Requirements, the team needs a document that details deliverables, boundaries, assumptions, and acceptance criteria before starting decomposition. Which process should they perform next?
- Validate Scope
- Define Scope
- Create WBS
- Control Scope
Correct Answer: B — Define Scope (develop the detailed description of the project and product)
Explanation: Define Scope uses requirements to produce the scope statement, which precedes Create WBS. Validate Scope and Control Scope occur later.
