PMP Course - Scope Management V2

Project Management Institute, A Guide to the Project Management Body of
Knowledge (PMBOK Guide), Fifth Edition, copyright 2013. Copyright and all
rights reserved. Material from this publication has been reproduced with the
permission of PMI
PMP Exam
Preparation Class
Qudratullah Hiwadpal, PMP
http://af.linkedin.com/in/hiwadpal/
BARYA CONSULTING SERVICES
www.barya.af/ training@barya.af
PMI, PMP and PMBOK, PM Network, PMI Today, PMI R.E.P, Project Management Journal are registered marks of the Project Management Institute, Inc.
Lesson SIX
Project Scope Management
Introduction
Create WBS
Scope Baseline
Validate Scope
Plan Scope
Control Scope
Management
Wrap UP
Collect Requirements
Test
Define Scope
Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Introduction
Project Scope Process Name Done During
Management Plan Scope Management Planning Process Group
includes the
processes required Collect Requirements Planning Process Group
to ensure that the Define Scope Planning Process Group
project includes all
the work required, Create WBS Planning Process Group
and only the work Monitoring and Controlling
Validate Scope
required, to Process Group
complete the project Monitoring and Controlling
Control Scope
successfully. Process Group
Managing the project scope is primarily concerned with defining

and controlling what is and is not included in the project.
Summary
Table of (ITTO)
for Scope
Management
A Guide to the Project Management Body of Knowledge, Fifth

Edition (PMBOK Guide) 2013 Project Management
Institute, Inc. Copyright and all rights reserved. Fig. 5-1,
Project Scope Management Overview, Page 106
Process in Scope Management
Scope can refer to
Product Scope: the required product, service

or result features and quality distinctions
Project Scope: what is required from the

project to deliver that scope

in a best world situation
(remember it for exam as well)
You must plan in advance, showing how will you determine, manage
and control the scope. This done during scope management plan.
Scope must be clearly defined and formally approved before work

starts.
Requirements are gathered from all the stakeholders, not just the
person who assigned the project.
A work breakdown structure (WBS) is used on all projects. using this

tool enables you to clarify identified scope as well as find additional
scope
Any change to the scope must be evaluated for its effect on time,
cost, risk, quality, resources and customer satisfaction.

in a best world situation
(remember it for exam as well)
While the project is being completed, you must check to make
sure you are doing all the work, but only the work included in
the project management plan.
Gold Platting a project is not allowed. (adding extra features)
No changes to scope are allowed without an approved

change request
Scope changes should not be approved if they relate to work

that does not fit within the project charter
You need to continuously determine what is and is not

included in the project
Scope Baseline
The scope baseline for the
project is the approved version of
the project scope statement, work
breakdown structure (WBS), and
its associated WBS dictionary.
A baseline can be changed only

through formal change control
procedures and is used as a
basis for comparison while
performing Validate Scope and Scope
Control Scope processes as well Baseline
as other controlling processes.

Plan Scope Management
Scope Management Plan
Three parts on scope (1) Planned (2) Executed (3) Controlled
Defining the following:
How to achieve the scope
What tools to use to plan how the project will accomplish the scope
How to create the WBS
What enterprise environmental factors and organizational process assets
How scope will be managed and controlled to the project management

plan
How to obtain acceptance to deliverables

Plan Scope Management
OUTPUT
Scope Management Plan
Requirements Management Plan
The requirements management plan is a component of the

project management plan that describes how requirements
will be analyzed, documented, and managed
May include:
Requirements prioritization
Product metrics
Traceability structure

Requirements are what stakeholders needs from a

project or product.
Collect Requirements is the process of

determining, documenting, and managing
stakeholder needs and requirements to meet
project objectives
The key benefit of this process is that it provides

the basis for defining and managing the project
scope including product scope

High level
requirements Need for
Change
identified in Project
Charter
Well documented
requirements Requirements
decreases chances Documentation
of change

TOOLS & TECHNIQUES
Historical Records Review:
Lessons Learned
Historical Records
Interviews
Expert Interviews
Focus Groups
TOOLS & TECHNIQUES
Facilitated Workshops
Different
stakeholders, with
various backgrounds
User Stories
As a <Role> I want
<Functionality/Goal>
so that <Business
Benefit/ Motivation>

TOOLS & TECHNIQUES
Brainstorming:
Nominal Group Technique:

TOOLS & TECHNIQUES
Mind Mapping
Affinity Diagram
TOOLS & TECHNIQUES
Multi-criteria Decision Analysis
Questionnaires and Surveys

TOOLS & TECHNIQUES
Observation
Prototype

TOOLS & TECHNIQUES
Context Diagram
Benchmarking

TOOLS & TECHNIQUES
Group Decision-Making Techniques
Majority
Plurality
Unanimity
Dictatorship
TOOLS & TECHNIQUES
Delphi Technique
Document Analysis

OUTPUT
Requirements Documentation
Business Requirements
Stakeholder Requirements
Solutions Requirements
Project Requirements
Transition Requirements
Requirements assumptions, dependencies and constraints

OUTPUT
Requirements
Traceability Matrix

Balancing Stakeholders Requirements
Resolving Competing Requirements

The business case for Project
Project Charter
Project Scope Statement
Project Constraints

Define Scope
TOOLS & TECHNIQUES
Expert Judgement
Product Analysis
Alternative Generation
Facilitated Workshops

Define Scope
OUTPUTS
Project Scope Statement:
The project scope statement is the description of
the project scope, major deliverables,
assumptions, and constraints
Deliverables
Includes:
Project Exclusion
Product scope
description Constraints
Acceptance Criteria Assumptions
Create WBS
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.

Create WBS
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.

Create WBS
some rules
WBS creation is a team effort.
Each level is smaller or detailed portion of

previous level
Entire project is included in each of the highest

levels of WBS, meaning some levels would further
broken down than others
Only project required deliverables are included,

so anything not in WBS is not part of the project

Create WBS
some rules
WBS is broken down until, each deliverable
can be realistically and confidently estimated
can be efficiently and effectively completed
can be completed without independently/

interruptions
can be outsourced or contracted out
can be monitored and measured

Create WBS
Control Accounts
Used to control cost, schedule and scope of group

of work packages
Each work package must be assigned to only ONE

control account
ONE control account can have many work packages

Create WBS
TOOLS & TECHNIQUES
Decomposition
Expert Judgement

Create WBS
TOOLS & TECHNIQUES
Rolling Wave Planning:
Wait until subcomponent is agreed, then

develop WBS
100% rule
Include everything (internal, external, interim)

Create WBS
OUTPUT
Scope Baseline:
WBS
WBS Dictionary
Scope Statement
Scope
Baseline
Project Document Updates

Validate Scope
TOOLS & TECHNIQUES
Inspection
Group Decision Making Technique

Validate Scope
OUTPUT
Accepted Deliverables
Change Requests
Work Performance Information
Project Document Updates

Control Scope
TOOLS & TECHNIQUES
Variance
Analysis

Wrap UP
Introduction to Scope Management
Processes Included in the Scope Management
Group Decision Making Techniques
Data Gathering Techniques
Decomposition
Scope Baseline
WBS dictionary

PMP Course - Scope Management V2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PMP Course - Scope Management V2

Uploaded by

Copyright:

Available Formats

Project Management Institute, A Guide to the Project Management Body of

Qudratullah Hiwadpal, PMP

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Managing the project scope is primarily concerned with defining

A Guide to the Project Management Body of Knowledge, Fifth

Scope can refer to

Product Scope: the required product, service

Project Scope: what is required from the

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Scope must be clearly defined and formally approved before work

A work breakdown structure (WBS) is used on all projects. using this

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Gold Platting a project is not allowed. (adding extra features)

No changes to scope are allowed without an approved

Scope changes should not be approved if they relate to work

You need to continuously determine what is and is not

A baseline can be changed only

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Three parts on scope (1) Planned (2) Executed (3) Controlled

Defining the following:

How to achieve the scope

How to create the WBS

What enterprise environmental factors and organizational process assets

How scope will be managed and controlled to the project management

How to obtain acceptance to deliverables

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Requirements Management Plan

The requirements management plan is a component of the

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Requirements are what stakeholders needs from a

Collect Requirements is the process of

The key benefit of this process is that it provides

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Nominal Group Technique:

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Multi-criteria Decision Analysis

Questionnaires and Surveys

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Requirements assumptions, dependencies and constraints

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Balancing Stakeholders Requirements

Resolving Competing Requirements

Project Scope Statement

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

The WBS organizes and

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

The planned work is contained within the lowest

A work package can be used to group the

In the context of the WBS, work refers to work

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

Each level is smaller or detailed portion of

Entire project is included in each of the highest

Only project required deliverables are included,

Qudratullah Hiwadpal, PMP, All Rights Reserved hiwadpal@barya.af

WBS is broken down until, each deliverable

can be realistically and confidently estimated

can be efficiently and effectively completed