8/9/2019 3_Edition5
1/31
8/9/2019 3_Edition5
2/31
8/9/2019 3_Edition5
3/31
•
Planning
•
Planning
•
Planning
•
Planning
•
Monitoring &
Controlling
•
Monitoring &
Controlling
8/9/2019 3_Edition5
4/31
Session Objectives… 1. To identify Project Scope Management
knowledge area processes2. How to plan scope management3. How to collect Requirements4. How to create Project Scope Statement5. How to create WBS and WBS Dictionary6. How to validate Scope the Deliverables
produced7. How to control Scope throughout the
Project
8/9/2019 3_Edition5
5/31
may be categorized as…
•Project Scope:-Product Scope:-
•The work needed to
create product of the
project
Features and functions of
the product of the project
•Completion of a
project is measured
against the plan
Completion of product
scope is measured against
the requirements
8/9/2019 3_Edition5
6/31
The process of defining and documentingcustomer needs
The customer requirements have to beelicited, analyzed and recorded
The Requirements are categorized as
• Product RequirementsProject Requirements
• Technical RequirementsBusiness Requirements
• Security RequirementsProject Management Requirements
• Performance RequirementsDelivery Requirements
8/9/2019 3_Edition5
7/31
Definition: The process of creating a scope management
plan that documents how the project scopewill be defined, validated, and controlled.
8/9/2019 3_Edition5
8/31
Input
• 1.Project
management
plan.
• 2. Project
Charter
• 3. Organizational
Process Assets
• 4. Enterprise
EnvironmentalFactors
Tools &
Techniques
• 1. Expert Judgment
• 2. Meetings
Output
• .1 Scope
management
plan
• .2 Requirements
management
plan
8/9/2019 3_Edition5
9/31
Contains..1. How requirements activities will be
planned, tracked and reported
2.
How configuration activities will beplanned, tracked and reported
3. Description of requirements prioritization
4. How product metrics are defined
5. How traceability structure is defined
8/9/2019 3_Edition5
10/31
Definition: The process of determining, documenting,
and managing stakeholder needs andrequirements to meet project objectives.
8/9/2019 3_Edition5
11/31
Input
• .1 Scope
management
plan
• .2 Requirements
managementplan
• .3 Stakeholder
management
plan
• .4 Project charter
• .5 Stakeholder
register
Tools &
Techniques
•.1 Interviews
•.2 Focus groups
•.3 Facilitated
workshops
•.4 Group creativitytechniques
•.5 Group decision-
making techniques
•.6 Questionnaires
and surveys
•.7 Observations
•.8 Prototypes
•.9 Benchmarking
•.10 Context diagrams
•.11 Document
analysis
Output
• 1. Requirements
Documentation
• 2. Requirements
Traceability
Matrix
8/9/2019 3_Edition5
12/31
Group Creativity Techniques1. Brainstorming
2. Nominal Group Techniques
3. Mind Mapping Group Decision Making Techniques
1. Unanimity
2. Majority
3. Plurality4. Dictatorship
8/9/2019 3_Edition5
13/31
Contains..
1. Business needs
2. Functional Requirements
3. Non-Functional Requirements4. Quality Requirements
5. Acceptance Criteria
6. Support and Training Requirements
7. Requirements Assumptions andConstraints
8/9/2019 3_Edition5
14/31
Definition: The process of developing a detailed
description of the project and product.
8/9/2019 3_Edition5
15/31
Input
•.1 Scope
management
plan
•.2 Project charter
•.3 Requirements
documentation
•.4 Organizational
process assets
Tools &
Techniques
•.1 Expert judgment
•.2 Product analysis
•.3 Alternatives
generation
•.4 Facilitated
workshops
Output
•1. Project Scope
Statement•2. Project
Document Updates
8/9/2019 3_Edition5
16/31
Project Scope Statement defines what workwill be performed and what work is excluded.
Project Scope Statement includes…
Project Scope Description
Product Acceptance Criteria
Project Deliverables
Project exclusions
Project Constraints & Assumptions
8/9/2019 3_Edition5
17/31
Definition: The process of subdividing project
deliverables and project work into smaller,more manageable components.
8/9/2019 3_Edition5
18/31
WBS decomposes the project work intosmaller, more manageable pieces of work.
WBS is a deliverable-oriented hierarchicaldecomposition of Project Work
Decomposition of project deliverables1. The major deliverables of the project are
identified, including project managementactivities
2. Determine if adequate cost and timeestimates can be applied to the lowestproject work.
8/9/2019 3_Edition5
19/31
WBSCost
Estimating
Risk
Management
Planning
Activity
Definition
Resource
Planning
Cost
Budgeting
•WBS is very important as it is input to5 core processes
8/9/2019 3_Edition5
20/31
Input
•.1 Scope
management
plan
•.2 Project scope
statement
•.3 Requirements
documentation
•.4 Enterprise
environmental
factors
•.5 Organizationalprocess assets
Tools & Techniques
•.1 Decomposition
•.2 Expert judgmen
Output
•.1 Scope baseline
•.2 Project documents
updates
8/9/2019 3_Edition5
21/31
roject
PM 1.1
1.1.1 1.1.2
1.1.2.1 1.1.2.2
1.1.2.2.1 1.1.2.2.2
HW 1.2
1.2.1
1.2.2
SW 1.3 SYS Eng 1.4 Testing 1.5 Database 1.6
Level- 1
Level- 2
Level- 4
Level- 5
Level- 3
8/9/2019 3_Edition5
22/31
Levels of WBS Project
o 1.1 Phase 1
1.1.1 Deliverable1.1.1.1 Deliverable
1.1.1.1.1 Work Package
WBS Identifier
8/9/2019 3_Edition5
23/31
Contains.. Code of accounts identifier.
Description of work.
Person / organization responsible to
completing the component.
List of schedule milestones.
Associated schedule activities.
Resources required & Cost estimates.
Quality requirements & Acceptance criteria.
Technical references.
8/9/2019 3_Edition5
24/31
Definition: The process of formalizing acceptance of the
completed project deliverables.
8/9/2019 3_Edition5
25/31
Validate Scope is the process of the projectcustomer accepting the project deliverables.
happens at the end of each project phase ora major deliverables are created
is ensuring that the deliverables the projectcreates are in alignment with the projectscope
Validate of Scope differs from quality control Quality control is preformed before validate
scope
8/9/2019 3_Edition5
26/31
Input
•1. Project
management
plan
•2. Requirements
•documentation•3.Requirements
traceability
matrix
•4.Verified
deliverables
•5. Work
performance
data
Tools & Techniques
•1. Inspection
•2. Group
decision-making
techniques
Output
•1.Accepted
deliverables
•2. Change
requests
•3. Workperformance
information
•4. Project
documents
updates
8/9/2019 3_Edition5
27/31
Definition: The process of monitoring the status of the
project and product scope and managingchanges to the scope baseline.
8/9/2019 3_Edition5
28/31
Project Scope Control concerned withinfluencing the factors that create projectscope changes and controlling the impact ofthose changes.
Scope control assures all requested changesand recommended corrective actions areprocessed through Integrated Change ControlProcess
Uncontrolled changes are referred to asScope Creep
8/9/2019 3_Edition5
29/31
Input
•.1 Project
management
plan
•.2 Requirements
documentation
•.3 Requirements
traceability
matrix
•.4 Work
performance
data
•.5 Organizational
process assets
Tools & Techniques
•.1 Variance
analysis
Output
•.1 Work
performance
information
•.2 Change
requests
•.3 Project
management
plan updates
•.4 Project
documents
updates
•.5 Organizational
process assets
updates
8/9/2019 3_Edition5
30/31
To Sum up… 1. We identified Project Scope Management
knowledge area processes2. We know how to plan scope management3. We know how to collect requirements4. We know how to create Project Scope
Statement5. We know how to create WBS and WBS
Dictionary6. We know how to validate Scope7. We know how to control Scope throughout the
Project
8/9/2019 3_Edition5
31/31