
Project scope = all the work (and only the work) needed to complete the project successfully.
Scope creep: Unauthorized addition of features or work without corresponding adjustments to time, cost, and resources. The #1 reason projects fail.
Key scope documents:
Scope Statement — describes deliverables, work included, and (critically) what is EXCLUDED
WBS (Work Breakdown Structure) — hierarchical decomposition of all project work into manageable components. Everything in the project must be in the WBS. Anything not in the WBS is out of scope.
WBS Dictionary: Defines each WBS work package — description, owner, acceptance criteria, resources, estimates.
Validate Scope: Formally accept completed deliverables with the customer. Different from quality control (internal verification).
Control Scope: Monitor status; manage changes to scope baseline. All scope changes go through integrated change control.
Requirements collection: Interviews, focus groups, surveys, prototyping, benchmarking. Requirements must be documented before defining scope.
Reference:
TaskLoco™ — The Sticky Note GOAT