CKPM202-Scope Management

Collect Requirements

Define Scope

Create WBS

Verify Scope

Control Scope

The features and functions that
characterize a product , service or result

The work that needs to be
accomplished to deliver a product, service or result with
the specified features and functions

The processes required to ensure that the
project includes all the work required and
only the work required to complete the project
successfully

Collect requirements is the process of defining and documenting
stakeholders’ needs to meet the project objectives

Inputs
• Project Charter
• Stakeholder
register

Tools and
Techniques
• Interviews
• Focus groups
• Facilitated workshops
• Group creativity
techniques
• Group decision
making techniques
• Questionnaires and
surveys
• Observations
• Prototypes

Outputs
• Requirement
documentation
• Requirement
Management
Plan
• Requirement
Traceability
Matrix

Requirement documentation
 Business need
 Business & project Objectives
 Functional requirement
 Non functional requirement
 Quality requirement
 Acceptance criteria
 Business rules
 Impacts to other organizational area & other entities
 Support & training
 Requirements assumptions and constraints

Is the process of developing a detailed
description of the project and product
 Detailed project scope statement is critical to
project success

Inputs
• Project Charter
• Requirements
documentation
• Organizational
process assets

Tools and
Techniques
• Expert judgment
• Product analysis
• Alternatives
identification
• Facilitated workshops

Outputs
• Project scope
statement
• Project document
updates

The Process of subdividing project deliverables and
Project work into smaller, more manageable
components in order to:
 Improve the accuracy of cost, time, and resource estimates
 Define a baseline for performance measurement and
control
 Facilitate clear responsibility assignments

Inputs
• Project scope
statement
• Requirements
documentation
• Organizational
process assets

Tools and
Techniques
• Decomposition

Outputs
• WBS
• WBS dictionary
• Scope baseline
• Project document
updates

1. A unit of work should appear at only one place in the WBS.
2. The work content of a WBS item is the sum of the WBS items below it.
3. A WBS item is the responsibility of only one individual, even though many people
may be working on it.
4. The WBS must be consistent with the way in which work is actually going to be
performed; it should serve the project team first and other purposes only if
practical.
5. Project team members should be involved in developing the WBS to ensure
consistency and buy-in.
6. Each WBS item must be documented to ensure accurate understanding of the
scope of work included and not included in that item.
7. The WBS must be a flexible tool to accommodate inevitable changes while
properly maintaining control of the work content in the project according to the
scope statement.

A work breakdown structure (WBS) is an
outcome-oriented analysis of the work
involved in a project that defines the total
scope of the project

It is a foundation document in project
management because it provides the basis
for planning and managing project schedules,
costs, and changes.

A deliverable-oriented grouping of project elements
which organises and defines the total scope of the
project.

Each descending level represents an increasingly
detailed definition of a project component.
 Project components may be products or services.

There are only two types of WBS items:
 Summary tasks
 Work packages: could be decomposed to activities

Scope verification is the process of
formalizing acceptance of the completed
project deliverables

Inputs
• Project
management plan
• Requirements
documentation
• Requirements
traceability matrix
• Validated
deliverables

Tools and
Techniques
• Inspection

Outputs
• Accepted
deliverables
• Change requests
• Project document
updates

Inputs
• Project management plan
•Work Performance
information
• Requirements
documentation
• Requirements traceability
matrix
•Organizational process
assets

Tools and
Techniques
• Variance analysis

Outputs
•Work performance
measurements
•Organizational process
assets updates
• Change requests
• Project management
plan updates
• Project documents
updates