TRADITIONAL KNOWLEDGE AREA
Scope management
Scope covers requirements, boundaries, breakdown, control, and acceptance.
The Eighth Edition groups content differently. Related topics can appear in several domains and chapters.
Understand the area
Define what work and deliverables are included, and establish how they will be accepted. Requirements express needs; product scope describes the resulting capability; project scope describes the work required. A breakdown structure makes the work manageable, while validation confirms formal acceptance. Avoid treating an attractive addition as authorized scope.
Work through a project
For a roadside barrier package, list the certified barrier type, terminal treatment, drawings, installation limits, inspections, exclusions and handover records. Decompose the installation into deliverables, then write acceptance criteria that the client and regulator can actually verify.
Check your reasoning
- Is this a requirement, a deliverable, or a work activity?
- Who accepts the deliverable and against which criterion?
- Does a requested addition require a controlled scope change?