Notes on Scope Management

Requirements Documentation
- Describes how the individual requirements will meet the business need for the project
- Must be measurable, testable, traceable, complete, and consistent
- Includes business, stakeholder, solution, transition, project, and quality requirements
- Traceability matrix links requirements from their origin through to the completion of the deliverables
Project Scope Statement
- Describes the project deliverables and the work required to create those deliverables
- Provides a common understanding of the project scope among the stakeholders
- Considered mandatory
WBS
- Graphical, hierarchical depiction of all the project work
- 100% rule: the lower levels roll up to the higher levels, nothing is left out
- Lowest level of a WBS is a work package

WBS Dictionary
- Companion document to the WBS, providing detailed information on the WBS components

Scope Baseline
- Includes the scope statement, the WBS, and the WBS dictionary
- Component of the project management plan

Decomposition
- Technique for creating the work breakdown structure (WBS)
- Subdivides the project deliverables into smaller, more manageable components
- May be structured by phase, location, or deliverable
- Hierarchical identification numbering is assigned based on the code of accounts / chart of accounts

Facilitated Workshops
- Attended by key cross-functional stakeholders
- Primary technique for defining cross-functional requirements
- Fosters relationships, builds trust, and improves communication
- Examples: joint application development or design (JAD) or quality function deployment (QFD) sessions