Project Scope Management
Domain 4 tests the six scope processes and, above all, whether you can tell product scope from project scope and verification from quality control. Case questions frequently describe a customer demanding extra features mid-project, and the expected answer is the change control path rather than informal accommodation.
The process chain
Planning scope management, collecting requirements, defining scope, creating the WBS, validating scope, controlling scope.
- Requirements tools: interviews, focus groups, facilitated workshops such as JAD, questionnaires, benchmarking, prototyping, brainstorming, nominal group technique, observation, document analysis, context diagrams.
- Outputs are the requirements document plus the requirements traceability matrix, which links each requirement to a deliverable, a test case, and a business objective.
Scope statement and WBS
- The project scope statement contains the product scope description, deliverables, acceptance criteria, and exclusions (项目除外责任). Exclusions prevent later disputes.
- The WBS is a deliverable-oriented hierarchical decomposition, not a schedule and not a list of activities.
- The 100% rule: the children of any node must fully define the parent, no more and no less.
- A work package is the lowest level, typically sized between 8 and 80 hours. A control account sits above work packages for cost and schedule roll-up; a planning package holds work not yet decomposed.
- The WBS dictionary defines each element's scope, acceptance criteria, and responsible party.
Validation and control
- Validate scope is formal acceptance of completed deliverables by the customer or sponsor; it follows quality control, which checks correctness.
- Control scope manages changes to the scope baseline. Scope creep is uncontrolled expansion; gold plating is voluntary extra functionality nobody requested. Both are defects.
Worked example
A data-centre project is decomposed into: civil works, power supply and UPS, cooling and ventilation, network cabling, fire and security, and project management. If the contract also requires operator training and no training element appears anywhere in the WBS, the decomposition violates the 100% rule even though every listed branch looks complete.
Traps that cost marks
- Confusing validate scope (customer acceptance) with control quality (conformance checking).
- Treating the WBS as an activity list or a schedule.
- Omitting exclusions from the scope statement.
- Accepting a verbal change request; scope changes go through integrated change control and the CCB.