Project scope management

Project scope management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully (PMBOK). It is mainly concerned with defining and controlling what is and is not included in the project.

Two kinds of scope are managed: product scope (features and functions of the product) and project scope (the work needed to deliver the product).

Processes (PMBOK 5th edition)

1. Plan scope management: create the scope management plan on how scope is defined, validated and controlled.
2. Collect requirements: determine and document stakeholder needs (interviews, workshops, surveys, prototypes).
3. Define scope: develop a detailed description of the project and product (project scope statement).
4. Create WBS: subdivide deliverables into smaller manageable components.
5. Validate scope: formal acceptance of completed deliverables by the customer.
6. Control scope: monitor the status of scope and manage changes to the scope baseline.

Plan scope -> Collect requirements -> Define scope
                -> Create WBS -> Validate -> Control

Key outputs

Scope management plan, requirements documentation, requirements traceability matrix, project scope statement, WBS and WBS dictionary (scope baseline), accepted deliverables, change requests.

Importance

• Prevents scope creep (uncontrolled expansion of scope).
• Gives a clear understanding to customer and team.
• Basis for schedule, cost and resource estimates.

Common problems

Incomplete requirements, unclear scope statement, no change control, gold plating.

Example: For an online exam system, scope includes question bank, exam delivery and result processing, but excludes admission management. Any request to add admission goes through scope change control.