PROJECT MANAGEMENT
CERTIFICATE PROGRAM
DEFINING PROJECT SCOPE
Module 5
1
2
Module Objectives
By module end, you will be able to:
• Understand how to define Scope
• Understand the purpose for using
– Collect Requirements
– Define Scope
– Create WBS
• Understand what tools will be used to
plan the Scope, Schedule, and Budget
3
Define Project Scope
4
• Define Project Scope is completed to
document the scope (work) of the
project
• When defining project scope, you
may be required to perform these
tasks:
– Record detailed customer
requirements
– Create the work breakdown
structure
Define Project Scope
During Define Project Scope,
3 PMBOK processes are used:
•Collect Requirements
•Define Scope
•Create WBS
5
Collect Requirements
• Defines and documents the product and
project features that are required to meet
stakeholder expectations and requirements
• “Requirements” are the conditions and
capabilities that must be achieved
• Requirements must be documented in
sufficient detail to allow measurement
• The identified expectations and requirements
will be used in other processes, such as cost,
quality, and schedule planning
6
Collect Requirements
This process defines and documents the project and product features and
functions needed to fill stakeholder’s needs and expectations
Inputs
Tools and Techniques

Project Charter

Interviews

Stakeholder

Focus Groups
Register

Facilitated Workshops

Group Creativity
Techniques

Group Decision Making
Techniques

Questionnaires and
Surveys
7

Observation

Prototypes
Outputs

Requirements
Documentation

Requirements
Management Plan

Requirements
Traceability Matrix
Collect Requirements
Think about the practical application
of this process :
• Process Documents
• Document Templates
• Process Tasks
• Think About It Exercise
8
MUST KNOW CONCEPTS
9
Define Scope
• Create the detailed project scope
statement.
• The Scope Statement provides
common understanding of the project
for the project stakeholders
• The Scope Statement is a narrative
document that is progressively
elaborated from the Project Charter
10
Define Scope
• Defines what is and is not included in
the project
• Project team and stakeholders must
have the same understanding of what
products will be produced and what
processes will be useD in producing
them
11
Define Scope
• Product Scope:
– Features and functions that
characterize the product, service,
or other project deliverable
– Processes, tools, and techniques for
managing product scope are
specific to the application area
12
Define Scope
• Project Scope:
– Work that must be done to deliver
the product with the features and
functions specified
– Generally accepted processes,
tools, and techniques for managing
scope are the subject of this course
13
Define Scope
This process defines and documents the project and product features and
functions needed to fill stakeholder’s needs and expectations
Inputs
Tools and Techniques

Project Charter

Expert Judgment

Requirements

Product Analysis
Documentation

Alternatives

Organizational Process
Assets
14
Identification

Facilitated Workshops
Outputs

Project Scope
Statement

Project Document
Updates
Define Scope
Think about the practical application
of this process :
• Process Documents
• Document Templates
• Process Tasks
• Think About It Exercise
15
MUST KNOW CONCEPTS
16
Create WBS
• Creates the detailed project work
breakdown structure
• Done by breaking the project down
into manageable pieces known as
work packages.
• The WBS is intended to show all of
the project work (scope). The WBS
shows work only – not time.
17
Create WBS (continued)
18
• WBS is a hierarchical, graphical
representation of the work. This forms
the scope baseline for the project.
• Derived from the Scope Statement and
the associated deliverables.
• A WBS dictionary may be used.
– Details specific elements of the work
packages depicted in the WBS.
Details such as who does the work,
skills, account codes, unique
definitions are included
Work Breakdown Structure
• A deliverable-oriented grouping of
project work that organizes and
defines the total scope of the project
• Work not in the WBS is outside the
scope of the project
19
• Used to develop and confirm a
common understanding of project
scope among stakeholders
Key Definitions
20
• Work Products:
– Anything tangible produced by the
project; includes Deliverables
• Deliverables:
– Specific, defined, and tangible
outputs from the project, that the
customer cares about
• Milestones:
– Collections of Major Work
Products or Deliverables, typically
used to measure project progress
Create WBS
This process subdivides major deliverables into manageable components
Inputs

Project Scope
Tools and Techniques

Decomposition
Outputs

Statement


Work Breakdown
Structure (WBS)
Requirements

WBS Dictionary
Documentation

Scope Baseline
Organizational Process

Project Document
Assets
21
Updates
Create WBS
Think about the practical application
of this process :
• Process Documents
• Document Templates
• Process Tasks
• Think About It Exercise
22
MUST KNOW CONCEPTS
23
MODULE REVIEW
24