Project Scope Management

PMBOKChapter5 1
1. Plan Scope Management

2. Collect Requirements

3. Define Scope

4. Create WBS

5. Validate Scope

6. Control Scope

PMBOKChapter5 2
1. Product Scope: The features and functions that characterize
a product, service, or result

2. Project Scope: The work performed to deliver a product,

service, or result with the specified features and functions.
The term project scope is sometimes viewed as including
product scope.

PMBOKChapter5 3
PMBOKChapter5 4
The process of creating a scope management plan
that documents how the project scope will be
defined, validated, and controlled.

PMBOKChapter5 5
Collect Requirements is the process of determining,
documenting, and managing stakeholder needs and
requirements to meet objectives. The key benefit of
this process is that it provides the basis for defining
the product scope and project scope.

PMBOKChapter5 6
PMBOKChapter5 7
PMBOKChapter5 8
PMBOKChapter5 9
PMBOKChapter5 10
PMBOKChapter5 11
The WBS is a hierarchical decomposition of the total scope of
work to be carried out by the project team to accomplish the
project objectives and create the required deliverables. The WBS
organizes and defines the total scope of the project and
represents the work specified in the current approved project
scope statement. The planned work is contained within the
lowest level of WBS components, which are called work
packages. A work package can be used to group the activities
where work is scheduled and estimated, monitored, and
controlled. In the context of the WBS, work refers to work
products or deliverables that are the result of activity and not to
the activity itself.

PMBOKChapter5 12
 Identifying and analyzing the deliverables and related work
 Structuring and organizing the WBS
 Decomposing the upper WBS levels into lower-level detailed
components
 Developing and assigning identification codes to the WBS
components; and
 Verifying that the degree of decomposition of the deliverables
is appropriate

PMBOKChapter5 13
PMBOKChapter5 14
PMBOKChapter5 15
PMBOKChapter5 16
The WBS is a hierarchical decomposition of the total scope of
work to be carried out by the project to accomplish the project
objectives and create the required deliverables.

PMBOKChapter5 17
1. Identifies all the work necessary
2. Identifies only the work necessary
3. Identifies specific work packages for estimating and
assigning work
4. Provides a structure for measuring success
5. Clarifies responsibilities
6. Forces detailed planning and documentation

PMBOKChapter5 18
 Planning
 Budgeting
 Funding
 Estimating
 Scheduling
 Performance measurement
 Configuration management
 Logistic support

PMBOKChapter5 19
1. Understanding the purpose of your project
2. Establish the major breakout segments of the work
3. Breakdown these large pieces into the next level of
components
4. Breakdown each component into subcomponents

5. Continue down to the level where you will assign and

monitor project work

6. Hold review session with core project team, client, and other
key stakeholders to gain buy-in and identify missing items

7. Prepare the WBS dictionary

PMBOKChapter5 20
 Work package

 Lowest level of the WBS

 Level where work is assigned and monitored
 Basic level for addressing schedules, costing, and resources
needed
 Cost / control account
 Typically a level above the work package
 Level for management reporting

PMBOKChapter5 21
 Provides detailed background on each work package
 Information about the activity, such as –
 Assumptions
 Specific activities at the work package level
 Resources
 Predecessors
 Successors

PMBOKChapter5 22
PMBOKChapter5 23
PMBOKChapter5 24
PMBOKChapter5 25
PMBOKChapter5 26
PMBOKChapter5 27
PMBOKChapter5 28
PMBOKChapter5 29
1 Scope Management process 11 Work Package
2 Scope baseline 12 Activity
3 Work Breakdown Structure 13 Project Scope
4 Project Scope Statement 14 Product Scope
5 WBS Dictionary 15 Decomposition
6 Requirements Documentation 16 Control Account
7 Requirements Traceability Matrix 17 Product Analysis
8 How to Create a WBS 18 Verified Documents
9 Uses of a WBS
10 Requirements Management Plan

PMBOKChapter5 30
19 Data Collection Techniques Group decision Making
Interviews Techniques
Focus Groups  Unanimity
Facilitated Workshops  Dictatorship
Group Creativity Techniques  Majority
 Brainstorming  Plurality
 Nominal Group Techniques Context Diagrams
 Multi-criteria Decision Document Analysis
Analysis
 Delphi Techniques
 Idea/Mind Maps
 Affinity Diagram
Questionnaires and survey
Observations PMBOKChapter5 31
20 Requirements Categories
Business requirements
Stakeholders requirement
Solution requirements
 Functional
 Non-functional
Transition requirements
Project requirements
Quality requirements
Technical requirements

PMBOKChapter5 32
Thank You

PMBOKChapter5 33