PMP Project Scope Management PMBOK V4.0

PMP Examination Preparation Course
Topic: Project Scope Management

Version 4.0
Project Scope Management
Hot Topics
Verify Scope
Project Charter
Work Breakdown structure

Scope Statement
Product Scope Decomposition
PMP Workshop | Financial Services

All work described was performed by Capgemini or a Capgemini affiliate
2009 Capgemini - All rights reserved 1
Project Scope Management includes the processes required to ensure that the
project includes all the work required, and only the work required, to
complete the project successfully.
The following Project Scope Management Processes are concerned with defining
and Controlling What is included and what is not included in the project:
Collect Requirements
Define Scope
Create WBS
Verify Scope
Control Scope

Project Scope Management processes are:
Monitoring &
Initiating Planning Executing Controlling Closing Process
Process Group Process Group Process Group Process Group Group
Collect Verify Scope
Requirement Control
Define Scope
Scope
Create WBS

Give the customer what they asked for,

Product Scope vs. Project Scope
no more or no less.
Giving extras is waste of time and adds
no benefit to the project
Scope
Product Project
Features or Functions Work to be done to deliver

product features/functions
Completion measured Completion measured against

against product requirements project plan

Project Scope Management Processes
Define Scope
Create WBS
Verify Scope
Control Scope

Collect requirement is the process of defining and documenting

stakeholders needs to meet the project objectives.
Projects success is directly influenced by the care taken in capturing and

managing project and product requirements.
Collecting requirements is defining and managing customer expectations
Requirements become the foundation of the WBS, Cost, Schedule and Quality
planning
The Requirements can be categorized into:
Project Requirements : Business requirements, Project management

Requirements, delivery requirements etc.,
Product Requirements : Information on technical requirements, Security
requirements, Performance requirements etc

Collect Requirements Data Flow

Inputs Tools and Techniques Outputs

Project Charter Interviews Requirements
Stakeholder Register Focus Groups Documentation
Facilitated Workshops Requirements

Management Plan
Group Creativity
Techniques Requirements
Traceability Matrix
Group decision
making Techniques
Questionnaires and
Surveys
Observations
Prototypes

Collect Requirements Inputs
1. Project Charter
High level Project requirements
High level Product Description
2. Stakeholder Register
Identify Stakeholders that can provide information on detailed project
and product requirements

Collect Requirements Tools and Techniques
1. Interviews 3. Facilitated Workshops
Formal or Informal information Bring cross functional stakeholders
discovery from stakeholders together to define product requirements
Performed by asking prepared and This can build trust, foster relationship
spontaneous questions and recording and improve communication leading to
responses increased stakeholder consensus
Often conducted one-on-one Example : Joint Application
2. Focus Groups Development (JAD session), Quality
function deployment (QFD) session.
Bring together prequalified
stakeholders and subject matter QFD starts by collecting customer
experts to learn about their needs, also known as Voice of
expectations Customer (VOC)
A trained moderator guides the group
through an interactive discussion

Collect requirements - Tools & Techniques
4. Group Creativity Techniques 6. Questionnaires and Surveys
Nominal Group Technique Written sets of questions designed to
Brainstorming accumulate information from wider
respondents
The Delphi Technique
Idea/mind mapping
7. Observation
Affinity Diagram
Viewing individual in their environment
5. Group Decision Making
Techniques Job Shadowing
Participant observer performing process
It is an assessment process of multiple
to uncover hidden requirement
alternatives with an expected outcome
in the form of future actions resolution.
Unanimity 8. Prototypes
Majority Working model of expected product
Plurality before actually building it
Dictatorship

Collect requirements Outputs
1. Requirements Documentation 2. Requirements Management Plan

Business Need or opportunity and Documents how requirements will be
Project Objectives analyzed, documented and Managed
Functional & Non Functional Details of how activities are planned,
requirements tracked and reported, Configuration
Quality requirements, Acceptance management activities, Requirements
Criteria, Business rules Prioritization, Product Metrics and
Traceability Structure etc.
Impact to other organization areas and
entities 3. Requirements Traceability Matrix
Support and Training requirement Links requirements to their origin and
traces the requirements to business
Assumptions and constrains need, opportunities, goals, objectives,
scope, product design, product
development, test strategy and test
scenarios, etc

Define Scope
Create WBS
Verify Scope
Control Scope

Define Scope
Define scope is the process of developing a detailed description of project

and product
Builds upon the Major deliverables, assumptions and constraints

The project scope is progressively elaborated during planning

Define Scope Data Flow

Define Scope

Project Charter Expert Judgment Project scope
Requirement Product Analysis statement
Documentation Alternative Project Document
Organizational Process identification updates
assets Facilitated workshops

Define Scope Inputs
1. Project Charter
High Level project description and product characteristics
Project approval requirements
2. Requirement Documentation
Described Earlier
3. Organizational Process Assets

Organizational policies, procedures, Templates for Project scope statement
Previous project files
Lessons Learnt from Previous Projects

Define Scope - Tools and Techniques
1. Expert judgment 3. Alternatives identification

Helps generate different approaches
Use of experts to develop scope to execute or perform work
statement
Examples of techniques
Example Other units of Brainstorming and Lateral thinking
Organizations, consultants,
Stakeholders, Professional and
4. Facilitated Work Shops
technical associations, Industry
groups, Subject Matter experts Described earlier
2. Product analysis
Methods used to translate project
objectives into tangible
requirements and deliverables
Examples Product breakdown,
systems engineering, systems
analysis, value engineering, value
analysis, functional analysis

Define Scope Outputs
1. Project Scope Statement 2. Project Document Updates

Forms basis of future project decisions Updates to
Helps develop common understanding Stakeholder Register
among stakeholders
Requirements Documentation
Is revised to reflect approved changes
Requirements traceability matrix
Includes or refers
Product Scope description
Product Acceptance Criteria
Project Deliverables
Project exclusions
Project Constraints
Project assumptions

Define Scope
Create WBS
Verify Scope
Control Scope

Create WBS
Create WBS is the process of subdividing project deliverables and Project

work into Smaller and more manageable components
Work Breakdown Structure (WBS)

Deliverable-oriented hierarchal decomposition of work to be executed by
project team to accomplish project objectives
Defines total scope of project and create required deliverables
Develops common understanding of the project scope
Each descending level provides more detailed description of the deliverable
Items at lowest level of WBS are called work-packages.
A work package can be scheduled, cost estimated, monitored and controlled

Create WBS Data Flow

Create WBS

Project Scope statement Decomposition WBS
Requirement WBS Dictionary
Documentation Scope baseline
Organizational process Project document updates
assets

Create WBS Inputs
1. Project scope statement

Described earlier
2. Requirement documentation
Described Earlier
3. Organizational process assets

Described earlier

Create WBS - Tools & Techniques
1. Decomposition
Decomposition is the subdivision of project deliverables into smaller, more
manageable components until the work and deliverables are defined to the
work package level
The work package level is lowest level in WBS, and is the point at which the
cost and activity durations for the work can be reliably estimated and
managed
Activities in Decomposition
Identify and analyze the deliverables and related work
Structuring and organizing the WBS
Decomposing to the required detailed level
Developing and assigning codes for WBS components
Verify the sufficiency of degree of decomposition

Create WBS Outputs
1. Work Breakdown structure 3. Scope Baseline
Described earlier The components of Scope baseline
are :
2. WBS Dictionary Project Scope statement
Supporting document containing WBS
details of WBS components. WBS Dictionary
It includes :
Code of account identifier 4. Project Documents update
Description of work Updates to Requirement
Responsible organization documentation.
Schedule milestones
Resources required
Cost estimates
Quality requirements
Acceptance criteria
Contract information

Define Scope
Create WBS
Verify Scope
Control Scope

Verify Scope
Verify Scope is the process of formalizing acceptance of the completed

project deliverables
Verifying scope includes reviewing deliverables with the customer or sponsor

It is done for ensuring completeness and obtaining formal acceptance
Verify scope Vs. Quality Control

Verify Scope is concerned with Acceptance of the deliverables
Quality Control is concerned with Correctness of the Deliverables

Verify Scope Data Flow

Verify Scope

Project Management Inspection Accepted deliverables
Plan Change Requests
Requirements Project document
Documentation updates
Requirements
Traceability Matrix
Validated deliverables

Verify Scope Inputs
1. Project Management Plan

The components of Scope baseline from Project management Plan include
Project scope statement, WBS, WBS Dictionary.
2. Requirements Documentation
Described earlier
3. Requirements Traceability Matrix

Described earlier
4. Validated Deliverables
Validated deliverables have been completed and checked for correctness by the
perform quality control process

Verify Scope - Tools & Techniques
Inspection
Activities such as measuring, examining, verifying performed to determine
whether work results or deliverables meet the requirements and the product
acceptance criteria
It includes supporting documentation received from customer or sponsor and
acknowledging stakeholder acceptance of projects deliverables.
Sometimes called reviews, product reviews, audits and walkthroughs

Verify Scope - Outputs
1. Accepted Deliverables
Documenting completed deliverables that are accepted
Documenting deliverables that are not accepted with reasons for non-
acceptance
Maintaining evidence (supporting documents) of stakeholder acceptance of
project deliverables
2. Change requests
Any changes that are requested in the Verify Scope process. These changes
will be reviewed through the Integrated change control process
3. Project Document Updates

Project documents that may be updated as a result of the verify scope process
include any documents that define the product or report status on product
completion

Define Scope
Create WBS
Verify Scope
Control Scope

Control Scope
Control Scope is the process of monitoring the status of the project and
product scope and managing changes to the scope baseline
Ensures that all requested changes and recommended corrective or

preventive actions are processed through Integrated change control process
Also used to manage the actual changes when they occur
Uncontrolled changes are often referred to as project scope creep

Control Scope Data Flow

Control Scope
Project Management Plan Variance analysis Work performance

Work Performance information
Information Organizational process
Requirements assets updates
Documentation Change requests
Requirements Traceability Project management Plan
matrix updates
Organization process Project documents
assets update

Control Scope Inputs
1. Project Management Plan 3. Requirements Documentation

The following information of Described earlier
project management plan used: 4. Requirements Traceability Matrix
Scope baseline
Described earlier
Scope management plan
5. Organizational process assets
Change management plan
Formal and informal scope control
Configuration management plan related policies, procedures and
Requirements management plan guidelines
2. Work Performance Information Monitoring and reporting method to be
used
Information about project progress
such as which deliverables started,
their progress and which is finished

Control Scope - Tools & Techniques
Variance Analysis
Performance measurement used to assess magnitude of variation
from original scope baseline.
Determining causes of variance from scope baseline & deciding
whether the variance warrants a corrective or preventive action

Control Scope - Outputs
1. Work Performance Measurement 3. Change Requests

Planned vs. actual technical Change requests to the scope
performance baseline or other components of
Other scope performance Project management Plan
measurements
Performance information is 4. Project Management Plan
documented and communicated to Updates
stakeholders
Scope Baseline Updates
Other Baseline Updates
2. Organizational Process Assets
Updates
5. Project Document Updates
Causes of Variances Requirements documentation
Corrective action chosen and the Requirements Traceability matrix
reasons
Lessons learnt from Scope control

Recap
Hot Topics
Verify Scope
Project Charter
Work Breakdown structure

Scope Statement
Decomposition
Product Scope

Review Questions Time
Review Questions

Thank You
www.capgemini.com/financialservices

PMP Project Scope Management PMBOK V4.0

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PMP Project Scope Management PMBOK V4.0

Caricato da

Copyright:

Formati disponibili

PMP Examination Preparation Course

Topic: Project Scope Management

Work Breakdown structure

Product Scope Decomposition

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Project Scope Management processes are:

PMP Workshop | Financial Services

Give the customer what they asked for,

Features or Functions Work to be done to deliver

Completion measured Completion measured against

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Collect requirement is the process of defining and documenting

Projects success is directly influenced by the care taken in capturing and

The Requirements can be categorized into:

Project Requirements : Business requirements, Project management

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Inputs Tools and Techniques Outputs

Facilitated Workshops Requirements

PMP Workshop | Financial Services

PMP Workshop | Financial Services

PMP Workshop | Financial Services

PMP Workshop | Financial Services

1. Requirements Documentation 2. Requirements Management Plan

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Define scope is the process of developing a detailed description of project

Builds upon the Major deliverables, assumptions and constraints

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Inputs Tools and Techniques Outputs

PMP Workshop | Financial Services

3. Organizational Process Assets

PMP Workshop | Financial Services

1. Expert judgment 3. Alternatives identification

PMP Workshop | Financial Services

1. Project Scope Statement 2. Project Document Updates

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Create WBS is the process of subdividing project deliverables and Project

Work Breakdown Structure (WBS)

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Inputs Tools and Techniques Outputs

PMP Workshop | Financial Services

1. Project scope statement

3. Organizational process assets

PMP Workshop | Financial Services

PMP Workshop | Financial Services

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Verify Scope is the process of formalizing acceptance of the completed

Verifying scope includes reviewing deliverables with the customer or sponsor

Verify scope Vs. Quality Control

PMP Workshop | Financial Services

PMP Workshop | Financial Services

Inputs Tools and Techniques Outputs

PMP Workshop | Financial Services

1. Project Management Plan

3. Requirements Traceability Matrix

PMP Workshop | Financial Services

PMP Workshop | Financial Services