Chap 5.3 define scope

Chapter 5 –
Project Scope Management
PMP
Trainer: Anand BobadePMBOK 6th Edition, 2019, All rights reserved.
Define Scope
SIXTH EDITION

PMBOK 6 - All rights reserved- 2019; By: Anand Bobade (nmbobade@gmail.com)
5.3. Define Scope
Process Overview
Define Scope process definition
How scope can lead to successful project.
Define Scope - ITTO
What is Product analysis?
Value engineering & Value analysis
What is Project scope statement?
Review

Scope Management processes
Plan scope
management
Collect
Requirements
Define Scope
Create WBS Validate Scope Control Scope
P P P
MC MCP

Define Scope -> Overview
Business requirements Stakeholder requirements
Solution requirements Transition requirements
Project requirements Quality requirements
Project scope
Statement
Requirements
documentation
Inclusion / Exclusion
Acceptance criteria's

Process of developing a detailed description of the project and
product.
Describes project, service or result boundaries by defining which
of requirements collected will be included & excluded.
Define Scope Definition
Detailed
Description
Project Scope
Statement
Requirements –
Inclusion &
exclusion

Scope &
project
success
Detailed &
unambiguous
scope.
Ensures all
assumptions and
constrained are
analyzed and
agreed.
It Improves
accuracy of Cost,
time & resource
estimates.
Helps in future
for detailed
resource
assignments
Define Scope -> Overview

5.3 – Define Scope Process ->ITTO
Expert Judgment
Data analysis
Decision Making
Interpersonal & team
skills
Product analysis
Project Charter
Project Management
plan
Project Documents
Enterprise
environmental factors
Organizational process
assets
Project Scope
statement
Project document
updates
Inputs Tools & Techniques Outputs

Define Scope-> Input
Project Charter
Project Management
plan
Project Documents
Enterprise
Organizational
process assets

Project charter is the first place to go for finding out about the scope of the
project.
Measurable objectives & success criteria's
High level requirements
High level project description
Project approval requirements
Define Scope-> Input -> Project Charter
Project Charter

Project
Management plan
Scope Management Plan
• It describes how scope will be Defined , Developed, Monitored,
Controlled & Verified.
It defines boundaries & framework to define the project scope.
Define Scope-> Input -> Project Management plan

Project Documents
Following Project Documents will provide input:
Define Scope-> Input -> Project Documents
Requirements
documents
Assumption log Risk Register
•It describes how individual requirements meet the business
need for the project.
Requirements
Document
•contains requirements related assumptions and other factors
that may influence the project and product scope.
Assumption
log:
•Risk can be mitigated through reducing or changing project or
product scope, outsourcing work to vendorsRisk Register:

Enterprise
EEF that can influence Monitor & Control Project Work
Define Scope-> Input -> EEF
Organization
structure
Organizational
Culture.
Marketplace
conditions
Personnel
administration

Organizational
process assets
OPA that can influence Define scope process are:
Define Scope-> Input -> OPA
Policies, processes &
Procedures
Project Documents
Lessons learned
Register

Define Scope-> Tools and Techniques
Expert Judgment Data analysis Decision Making
Interpersonal &
team skills
Product analysis

Define Scope-> T&T-> Expert Judgment
Subject mater
experts
Consultants &
Contractors
Stakeholders,
(customers or
sponsors)
Professional and
technical
associations
Industry groups
Other units
within the
organization
The experts with experience in similar projects, can help define scope.
Helps include & exclude requirements.
Expert Judgment

Data analysis
Alternative analysis:
• It is the evaluation of the different choices available to
achieve a particular product requirement.
Define Scope-> T & T -> Data analysis

Decision
Making
Define Scope-> T & T -> Decision Making
Multi-criteria decision analysis:
Uses a decision MATRIX to provide a systematic approach
for setting criteria, such as schedule, budget, resources, to
rank the various alternative to meet the requirements.

Interpersonal &
team skills
Facilitation:
• Help develop common understanding of the project
deliverables and project/product boundaries with cross
functional teams.
Define Scope-> T & T -> Interpersonal & team skills
Joint Application
development (JAD):
Quality Function
Deployment (QFD)
User stories

Product Analysis
Product analysis can be an effective tool to evaluate product. Especially, when product is
output of the project.
Improve the project teams understanding of the Product.
Translating high-level product descriptions into tangible deliverables.
Product Breakdown System analysis Requirements analysis
System engineering Value engineering Value analysis
Define Scope-> T & T -> Product Analysis

Product Analysis
Product Breakdown
• The requirements are decomposed into the level of detail
needed to design the final product.
Requirements analysis
• Defined to a level of detail sufficient for system design.
• Requirements should be actionable, measurable, testable,
traceable etc
System analysis
• It relates closely to requirements analysis.
• The process of studying a business in order to identify its
goals and purposes and create systems and procedures
System engineering
• Ensure that the product satisfies customer needs, cost
requirements, and quality demands.

Product Analysis
Product Analysis Techniques:
•Optimize the overall value of
the project from inception to
operations.
•Aim is to achieve the lowest
life cycle cost by considering
alternative designs.
Value engineering:
•Cost reduction tool that
considers whether function is
really necessary.
•Finding least expensive way
to deliver scope.
•Developing function at a
lower cost without
degrading performance or
quality (Cost of Quality)
Value analysis:

Project scope
Statement
Project documents
updates
Define Scope-> Output

Project scope
Statement
It is the description of the project scope major deliverables, Assumptions & Constraints
Product scope
description
Deliverables
Acceptance
Criteria
Inclusion/
Exclusions
Constraints &
assumptions
Define Scope-> Output -> Project scope Statement
# Requirements/ Deliverables
Description
Priority Project
Objective
WBS
Deliverable
Inclusion /
Exclusion
1 Secure Login process Medium Objective 1 1.1.1 Included
2 Payroll processing High Objective 3 1.3.1 Included
3 Send payroll instructions to banks High Objective 3 1.3.2 Included
4 Send Tax deductions to Govt. tax
dept.
Low Objective 3 1.3.3 Excluded

Project scope
Statement
• Characteristics –
Product, Service or
Result.
Product
scope
description
• Unique – Product,
Service or Result.
Deliverables
• All required conditions
that need to be meet to
accept the deliverables.
Acceptance
Criteria

Project scope
Statement
• What is excluded from
project scope.
Exclusions
• Limits that impact project
execution or
product/service delivery.
Constraints
• Factors assumed to be
true for defining/finalizing
project scope statements.
Assumptions

Project Charter
Project Purpose or Justification
Measurable obj & success
criteria's
High level requirements
description
Summary milestone schedule
Stakeholder list
Project approval requirements
Project scope Statement
Project scope description
Acceptance criteria
Project deliverables
Project exclusions
Project constraints
Project assumptions

Project documents
updates
Below project documents may get updated
Assumption log Requirements documents Stakeholder Register
Define Scope-> Output->Project documents updates

Define Scope-> Review
Process Overview
Define Scope process definition
How scope can lead to successful project.
Define Scope - ITTO
What is Product analysis?
Value engineering & Value analysis
What is Project scope statement?

Chap 5.3 define scope

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Chap 5.3 define scope

Similar to Chap 5.3 define scope (20)

More from Anand Bobade

More from Anand Bobade (9)

Recently uploaded

Recently uploaded (17)

Chap 5.3 define scope