Project Scope Management Processes

Project Scope Management

Consists of the processes to guarantee that the project contains only the work necessary to effectively carry out the project; involves defining and controlling project inclusions and exclusions.

Product Scope

Describes the features or characteristics of a product regardless of design, function, or parts; refers to the actual tangible product that is made.

Project Scope

Concentrates on the various steps taken to deliver a product (e.g., assembly lines, budgets, staff training, supply chains, and personnel allocations).

6 Project Scope Management Processes

1. Plan Scope Management, 2. Collect Requirements, 3. Define Scope, 4. Create WBS, 5. Validate Scope, 6. Control Scope.

Plan Scope Management (Definition)

The process that documents how the project and product scope will be defined, validated, and controlled.

Plan Scope Management (Key Benefit)

Offers guidance and direction on how the scope will be managed throughout the project.

Plan Scope Management (Outputs)

1. Scope Management Plan, 2. Requirements Management Plan.

Scope Management Plan

A plan documenting how the project and product scope will be defined, developed, monitored, controlled, and validated.

Requirements Management Plan

A plan documenting how project and product requirements will be analyzed, documented, and managed.

Collect Requirements (Definition)

The process that determines, documents, and manages stakeholder requirements and expectations to meet project goals.

Collect Requirements (Key Benefit)

Offers a basis for defining the product scope and project scope.

Collect Requirements (Outputs)

1. Requirements documentation, 2. Requirements Traceability Matrix.

Requirements Documentation

Defines how individual requirements meet business needs; should be clear, traceable, complete, consistent, and acceptable to key stakeholders.

Requirements Traceability Matrix

A grid-like instrument connecting product requirements from their origin to deliverables that satisfy them, enabling tracing throughout the life cycle.

Define Scope (Definition)

The process that separates final project requirements from collected requirements and develops a detailed description of the project, product, service, or outcome.

Define Scope (Key Benefit)

Describes the product, service, or result boundaries and acceptance criteria.

Define Scope (Outputs)

1. Project Scope Statement, 2. Project Documents Updates.

Project Scope Statement

Consists of detailed project scope description, major deliverables, assumptions, constraints, and explicit scope exclusions.

Product Scope Description

Sub-component of the Project Scope Statement describing features of the product, service, or outcome detailed in the charter and requirements.

Deliverables (Define Scope)

Any distinctive and independently verifiable output, outcome, or service-delivery capacity needed to finish a procedure, stage, or undertaking.

Acceptance Criteria

Conditions required to be met for the acceptance of deliverables.

Project Exclusions

Specific statements of the parts and concepts that are not included in the known scope of the project.

Define Scope (Project Documents Updates)

1. Assumption log, 2. Requirements documentation, 3. Requirements traceability matrix, 4. Stakeholder register.

Create WBS (Definition)

The process that subdivides deliverables and project work into smaller, more manageable parts.

Create WBS (Key Benefit)

Provides a framework of what has to be delivered.

Create WBS (Outputs)

1. Scope Baseline, 2. Project Documents Updates.

Scope Baseline

The accepted version of a scope statement, WBS, and associated WBS dictionary; modified only through formal change control procedures.

Create WBS (Project Documents Updates)

1. Assumption log, 2. Requirements documentation.

Work Breakdown Structure (WBS)

Offers a hierarchical structure of project activities focusing on 'work' rather than 'things'; answers 'How are products made?' and represents 'VERBs'.

Product Breakdown Structure (PBS)

A hierarchical structure of deliverables the project creates; represented as a project 'shopping list'; answers 'What is this product made of?' and stands for 'NOUNS'.

WBS vs. PBS (Key Difference)

WBS represents project 'work/activities' (VERBs), while PBS represents deliverable 'things' (NOUNS).

Validate Scope (Definition)

The process that formalizes acceptance of completed deliverables through customer, stakeholder, or manager reviews and approvals.

Validate Scope (Key Benefit)

Delivers objectivity to the acceptance process and increases probability of final product/service/result acceptance.

Validate Scope (Outputs)

1. Accepted Deliverables, 2. Work Performance Information, 3. Change Requests, 4. Project Document Updates.

Accepted Deliverables

Deliverables meeting acceptance criteria that are formally signed off and approved by the customer or sponsor.

Work Performance Information (Validate Scope)

Information regarding progress, detailing which deliverables have or have not been accepted and why.

Change Requests (Validate Scope)

Requests generated for defect repair when completed deliverables are not appropriately accepted.

Validate Scope (Project Document Updates)

1. Lessons learned register, 2. Requirements documentation, 3. Requirements traceability matrix.

Control Scope (Definition)

The process of monitoring project/product status, scope, and changes to the scope foundation to ensure execution matches the scope management plan.

Control Scope (Key Benefit)

Ensures the scope baseline is maintained throughout the project.

Control Scope (Outputs)

1. Work Performance Information, 2. Change Requests, 3. Project Management Plan Updates, 4. Project Document Updates.

Work Performance Information (Control Scope)

Correlated and contextualized information on how project/product scope is performing compared to the scope baseline.

Control Scope (Project Document Updates)

1. Lessons learned register, 2. Requirements documentation, 3. Requirements traceability matrix.

Process Group Mapping: Planning Group

5.1 Plan Scope Management, 5.2 Collect Requirements, 5.3 Define Scope, 5.4 Create WBS.

Process Group Mapping: Monitoring & Controlling Group

5.5 Validate Scope, 5.6 Control Scope.