PMP Scope - 3rd Edition

Institut de Formation
INSTITUT DE FORMATION
Tous droits réservés. Reproduction intégrale ou partielle interdite sans autorisation écrite de la part du titulaire des droits d’auteur.
Session de préparation à l’examen de
certification PMP
Project Scope
Management
Version 2.0 - Août 2005

Scope Management
1. Introduction
2. Scope planning
3. Scope definition
4. Create WBS
5. Scope verification
6. Scope change control
7. Questions
Version 2.0 - Août 2005 Project Scope Management 2

Introduction
Definitions
• Project Scope Management includes the processes

required to insure that the project includes
all the work required, and only the work required,
to complete the project successfully
• It is primarily concerned with controlling what is or is
not included the project

Introduction
Definitions
• Product scope
• The features and functions that characterize product or service.
• It is measured against the product requirements.
• Project scope
• The work that must be done in order to deliver the product with the
specified features and functions.
• It is measured against the project scope statement.

Introduction
Processes
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Initiating Processes
Planning
Integration processes
Develop project
charter
Executing
processes
Integration
Develop preliminary
project scope
statement
Monitoring &
controlling
processes

Planning Processes
Integration Scope Scope
Develop project Scope Scope Monitoring &
management plan planning definition
Initiating controlling
Time processes
processes Scope Activity
Time
Create WBS Activity resource definition
estimating
Time
Risk Cost Activity duration
Risk management Cost estimating estimating
planning
Risk Cost
Risk Cost budgeting
identification
Time
Human Resources Activity
Risk Human resource sequencing
Qualitative planning
Risk analysis
Quality Time
Risk Quality Schedule
Quantitative planning development
Risk analysis
Communications
Communications Executing
planning processes
Procurement Procurement
Plan purchases Plan contracting
and acquisitions
Closing
Risk
Risk response processes
planning

Executing Processes
Monitoring &
Quality controlling
Perform quality
assurance processes
Initiating
processes Human Resources
Acquire project
team
Integration Human Resources Communications

Direct and manage Develop project Information
project execution team distribution
Procurement Procurement
Request seller Select seller
Planning responses
Closing
processes
processes

Controlling Processes
Scope
Scope
verification
Scope
Initiating Scope control
processes
Integration Time
Monitor & control Schedule
project work control
Cost
Cost
control
Quality
Perform quality
Planning control Closing
Procurement
processes Contract processes
administration
Human Resources
Manage project
team
Integration Communications
Integrated change Manage
control stakeholders
Risk
Executing Risk monitoring
And control
processes Communications
Performance
reporting

Closing Processes
Planning
processes
Integration
Close project
Executing
processes
Procurement
Contract
Closure
Monitoring &
controlling
processes

Scope Planning
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Scope Planning
Definition
Process of creating the scope
management plan, that describes :
• how the project scope will be defined, verified
and controlled
• how the WBS will be created

Scope Planning
Inputs I
• Enterprise environmental factors

• Culture, HR, marketplace…
• Organizational process assets
• Organizational policies and procedures
• Historical information (KB)
• Project charter From Project

Integration
• Preliminary scope statement Management
• Project management plan

Scope Planning
Tools and techniques T
• Expert judgment
• Templates, forms, standards
• Scope management plan templates
• WBS templates
• Scope change control forms…

Scope Planning
Outputs
O
• Scope Management Plan
Describes how project scope will be
defined, verified and controlled :
• How scope statement will be detailed
• How WBS will be created, maintained and approved
• How verification and acceptance of deliverables will be obtained
• How scope changes will be integrated (Integrated Change
Control)
Benefits :
• Limit scope creep
• Limit conflicts and scope changes
• Improved communications
• Improved customer satisfaction

Scope Planning
Project
charter
Develop Project Scope
Charter Planning Scope
Prelim. scope stmt
Scope Verification
management plan
Prelim. proj.
scope statement
Scope
Project mgt plan
Definition Scope
Develop Project Control
Management Plan
Create WBS
See detailed figure PMBOK p. 106

Scope Definition
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Scope Definition
Definition
Process of creating the (detailed)
project scope statement, that describes :
• the project’s deliverables,
• what work will be performed to create those
deliverables
• what work will be excluded

Scope Definition
Inputs I

• Project charter
• Preliminary scope statement

• If not existing, similar information should be collected
• Includes product scope description
• Scope management plan
• Approved change requests

Scope Definition
• Product analysis
• product breakdown,
• systems engineering / system analysis
• value engineering
• functional analysis
• Alternatives identification
• brainstorming
• lateral thinking
• Expert judgment
• Stakeholder analysis

Scope Definition
Value engineering
A methodology that focuses on the function of a material, process or service in

providing value to the customer. It attempts to define cost, quality and customer
acceptance parameters in determining the value and possible redesign or
reengineering of a given function
An methodology that identifies and selects the lowest life cycle cost options in
design, materials and processes that achieves the desired level of performance,
reliability and customer satisfaction. It seeks to eliminate unnecessary costs in the
above areas and is often a joint effort with cross-functional internal teams and
relevant suppliers.
Value Engineering : PMBOK p. 379

Scope Definition
W hich of the following is a tool for analyzing a design, determining its

functions, and assessing how to provide those functions cost effectively ?
A Pareto diagram
B Value analysis
C Configuration management
D Value engineering

Scope Definition
Outputs O
• Scope statement
• Includes project…
• objectives (including measurable success criteria)
• deliverables
• requirements, boundaries, constraints and assumptions
• initial organization, initial defined risks, schedule milestones,
fund limitation, cost estimate, configuration mgt requirements,
project specification documents required, approval requirements.
• Includes product…
• scope description, acceptance criteria
• Scope management plan (Updates)

• Requested changes

Scope Definition
A scope statement is important because it :
A Provides the basis for future project decisions

B Provides a brief summary of the projet
C Approves the project for the stakeholders
D Provides criteria for measuring project cost

Scope Definition
Project
Develop Project charter Scope
Charter Planning Scope
Prelim.
Scope statement
Scope
management plan
Verification
Prelim. proj.
scope statement
Scope
Definition Scope
Approved
Develop Project Change
Requests
Control
Scope + Scope
Management Plan Requested statement management plan
changes (Updates)
Integrated Change Create WBS

Control
Create WBS
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Create WBS
Subdivision of the major project deliverables into
smaller and more manageable pieces of work, to :
• Improve cost, duration and resource estimates
accuracy
• Define a baseline for performance measurement and
control
• Facilitate clear responsibility assignments

Create WBS
Definitions
The WBS is a deliverable-oriented hierarchical decomposition of
the work to be executed by the project team (or performing
organization), to accomplish the project objectives and create the
required deliverables.
It organizes and defines the total scope of the project.
 Work Components
 Work Packages
 WBS Dictionnary
 OBS = Organizational Breakdown Structure

Create WBS
Definitions (cont’d)
Level 0 WBS PROJECT
Level 1 DELIVERABLE 1 DELIVERABLE 2 DELIVERABLE 3
Level 2 WORK COMP. 1.1 WORK COMP. 1.2 WORK COMP. 1.3
Work package
OBS
Level 3 TASK 1.1.1 TASK 1.1.2 TASK 1.1.3
Feasibility Analytical Control account
Design Technical Control account
Testing Production Control account
and …RAM
Create WBS
Definitions : characteristics of the WBS
• Created with the help of the team
• Complete a level before detailing further
• Not chronologically oriented
• Each level is a smaller segment of level above
• Work not in WBS is not in the project
• Generally decomposed as follows :
project name
deliverables, phases of the project life cycle, or subprojects
work components..
work packages

Create WBS
Definitions : characteristics of the WP
• Each item has a unique identifier
• Assigned to a single organizational unit
• Can be scheduled and budgeted
• Can be described in terms of tangible, measurable
results
• Lowest level of each branch of the WBS
• Level at which performance measurement is
executed (e.g. EVM) : control account

32
Create WBS
Definitions : other structures
Project Scope Management

• CWBS
• BOM
• RBS

Create WBS
A work breakdown structure is most similar to a :
A Resource breakdown structure

B Bill of materials
C Organizational breakdown structure
D Contractual breakdown structure
E Project breakdown structure

Create WBS
Inputs I
• Scope statement (including deliverables)

• Approved change requests

Create WBS
• Work Breakdown Structure templates

= WBS from previous projects
• Decomposition
1. Identify major deliverables and related work
2. Decide if adequate cost & duration can be determined
3. Identify constituent components of the deliverable
Work Components
Work Packages at lowest level
Read PMI Practice Standard for WBS

Create WBS
Decomposition
1. Identify
Deliverable
2. Can we estimate
cost and schedule ? 3. Identify constituent
components of the deliverable
No
Yes
4. Verify correctness
of decomposition

Create WBS
Outputs O
• WBS
• WBS dictionary = Scope Baseline !
• Scope statement (updates)
• Scope management plan (updates)
• Requested changes (forgotten, added work that needs to
gain approval through integrated change control process)
And Now… Communicate !

Create WBS
Scope
Planning Scope
Verification
Scope
Definition Scope
Develop Project Control
Management Plan Scope + Scope
Statement Management Plan
Approved
Change
Requests
Integrated Change
Control Create WBS WBS + WBS Dictionnary
Scope Statement (Updates)
Requested
changes Scope Management Plan (Updates)

Create WBS
WBS Dictionary
• Code of account unique id
• SOW = Statement of Work
• Deliverable(s)
• List of associated activities
• List of milestones
and…
• Responsible Organization
• Start and end date
• Resources required
• Estimate of cost
• Contract information
• Quality requirements
• Technical references

Create WBS
A precise description of a deliverable is called a :
A Specification
B Baseline
C Work package
D Work breakdown structrure component
Any numbering system that is used to monitor project costs by category such
as labor, supplies, or materials, for example, is called :
A Chart of accounts
B Work breakdown structure
C Universal accounting standard
D Standard accounting practices

Create WBS
The product scope is measured against :
A Project scope
B Projet plan
C Product requirements
D Work breakdown structure
A project manager is reviewing the work breakdown structure for her project.
The WBS for the project represents :
A All the tangible items that must be delivered to the client.

B All the work that must be completed for the project.
C The work that must be performed by the project team.
D All the activities of the project

Create WBS
A new project has begun. The project charter has been written and the project
manager has been assigned. The project manager is preparing the work
breakdown structure for the project. The WBS is typically used for:
A Explaining the scope of the project relevant to the client

B The basis for organizing and defining the total scope of the project
C Showing the resource conflicts that exist in the project
D The logical relationship between tasks in the project

Scope Verification
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Scope Verification
Definition
• Obtaining formal acceptance of the project scope
and deliverables by the stakeholders
• Requires reviewing deliverables and work results to
ensure all were completed
Note
• Scope verification is concerned with acceptance of work
results
• Quality control is concerned with correctness of work results

Scope Verification
Inputs I
• Scope statement
(deliverables description + acceptance criteria)
• Work Breakdown Structure dictionary
• Deliverables
(fully or partially completed)

Scope Verification
• Inspection
• Measuring
• Examining
Also called reviews, product

reviews, audits, walkthroughs

Scope Verification
Output O
• Accepted deliverables
Document accepted / non accepted
ones with list of reasons
For review in Integrated change
control process
• Recommended corrective actions
Scope Verification
Scope
Planning Scope Deliverables
Direct and Manage
Verification project execution
Requested changes
Accepted Deliverables + Recommended
Scope corrective actions
Definition Scope Integrated Change

Control Control
Scope + Scope
statement management plan
WBS dictionnary
Create WBS

Scope Verification
Configuration management is a technique used for :
A Overall change control

B Project plan execution
C Scope planning
D Risk quantification
Due to cuts in funding, your project has terminated. The scope verification
process :
A Should be delayed until the project is completed

B Should determine the correctness of work results
C Should establish and document the level of extent of completion
D Will form a basis of the project audit

Scope Control
Scope
Planning Scope
Verification
Scope
Definition Scope
Control
Create WBS

Scope Control
Definition
Controlling changes to the project scope :
• Influencing the factors which create project scope
changes (to ensure that they will be agreed upon)
• Controlling the impact of changes
• Assuring all “requested changes” and
“recommended corrective actions” are processed
through ICC
• Managing actual changes when they occur

Scope Control
Inputs I
• Scope statement
• WBS
• WBS dictionary
• Approved change requests (documented)
• From an external event
• An error or omission in product’s scope definition
• An error or omission in project’s scope definition
• A value-adding change
• Implementing a risk response
• Work performance information

• Performance reports
Scope Control
• Configuration Management System
• used to provide status of the deliverables and document
requested changes to project and product scope
Integrated Change Control
• Change Control system

• used to define and document scope change requests

Scope Control
Tools and techniques (cont’d) T
• Variance analysis
• assess magnitude of variations compared to baseline
• determine the cause of variance
• decide whether (recommended) corrective action is required
• Replanning Integrated Change Control
• update scope documentation to take account of Approved change requests :

• Scope statement
• WBS, WBS dictionary
• Scope management plan Project management plan

Scope Control
Outputs O
• Scope statement (Updates)
Scope baseline updates
• WBS (Updates)
• WBS dictionary (Updates)
• Project management plan (Updates)
• Must be notified to all stakeholders
• Recommended corrective action
• Organizational process assets (Updates)

Scope Control
Performance Reports
Scope (from Communications)
Planning Scope Direct and Manage

Verification project execution
Work Performance Information

Scope + Scope
Scope statement management plan
WBS / WBS dictionnary
Definition
Scope Approved
Change Integrated Change
Control Requests
Control
Scope Requested changes
statement (U) + Recommended corrective actions
Create WBS WBS (U) + WBS dictionnary (U)
Project Management Plan (U)

Scope Control
Two months into a five-month software development project, the client
approaches your company with new specifications that forces you to perform
scope changes. You must now review the :
A Scope change control system

B Assumptions document
C Organizational policies document
D Work breakdown structure document
You have just taken control of a project in the middle of execution and need to
learn who has approval authority for revisions in scope. Which document
provides the information ?
A Resource assignement matrix

B Scope management plan
C Project charter
D Client organization chart

Scope Control
All of the following assist in determining the impact of a scope change,

EXCEPT :
A Project charter
B Baseline
C Performance measurement
D Milestones
Scope Control must be integrated with all of the following processes EXCEPT :
A Schedule
B Cost
C Procurement
D Quality

Scope Control
A project manager is reviewing the scope of the project and the scope
baseline of the project. This includes which of the following?
A The original project schedule, budget, and scope

B The original project description and the project charter
C The original scope of the project plus or minus any scope changes
D The current budget of the project
During the course of the project it is important that the stakeholders be

informed of the progress of the project. One of the reports that is frequently
used is a progress report. Which of the following is true about progress reports
?
A They allow stakeholders to judge the performance of the project according to

its plan
B They are generally considered to be overkill on very small projects
C They require the use of earned value reports
D They must be produced by the project manager

Scope Management
Scope management means
• Check if you’re completing all the work
• No gold plating
• Say no to work not included in the project
Give the customer what they asked for,

no more, no less

61
Test : scope

62
Scope Management

Questions ?

PMP Scope - 3rd Edition

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PMP Scope - 3rd Edition

Diunggah oleh

Hak Cipta:

Format Tersedia

Institut de Formation

Version 2.0 - Août 2005

Version 2.0 - Août 2005 Project Scope Management 2

• Project Scope Management includes the processes

Version 2.0 - Août 2005 Project Scope Management 3

Version 2.0 - Août 2005 Project Scope Management 4

Version 2.0 - Août 2005 Project Scope Management 5

Version 2.0 - Août 2005 Project Scope Management 6

Version 2.0 - Août 2005 Project Scope Management 7

Integration Human Resources Communications

Version 2.0 - Août 2005 Project Scope Management 8

Version 2.0 - Août 2005 Project Scope Management 9

Version 2.0 - Août 2005 Project Scope Management 10

Version 2.0 - Août 2005 Project Scope Management 11

Version 2.0 - Août 2005 Project Scope Management 12

• Enterprise environmental factors

• Project charter From Project

Version 2.0 - Août 2005 Project Scope Management 13

Version 2.0 - Août 2005 Project Scope Management 14

Version 2.0 - Août 2005 Project Scope Management 15

See detailed figure PMBOK p. 106

Version 2.0 - Août 2005 Project Scope Management 16

Version 2.0 - Août 2005 Project Scope Management 17

Version 2.0 - Août 2005 Project Scope Management 18

• Organizational process assets

• Preliminary scope statement

• Approved change requests

Version 2.0 - Août 2005 Project Scope Management 19

Version 2.0 - Août 2005 Project Scope Management 20

A methodology that focuses on the function of a material, process or service in

Value Engineering : PMBOK p. 379

Version 2.0 - Août 2005 Project Scope Management 21

W hich of the following is a tool for analyzing a design, determining its

Version 2.0 - Août 2005 Project Scope Management 22

• Scope management plan (Updates)

Version 2.0 - Août 2005 Project Scope Management 23

A scope statement is important because it :

A Provides the basis for future project decisions

Version 2.0 - Août 2005 Project Scope Management 24

Integrated Change Create WBS

Version 2.0 - Août 2005 Project Scope Management 26

Version 2.0 - Août 2005 Project Scope Management 27

Version 2.0 - Août 2005 Project Scope Management 28

Level 1 DELIVERABLE 1 DELIVERABLE 2 DELIVERABLE 3

Feasibility Analytical Control account

Design Technical Control account

Testing Production Control account

Version 2.0 - Août 2005 Project Scope Management 30

Version 2.0 - Août 2005 Project Scope Management 31

Project Scope Management

Version 2.0 - Août 2005

A work breakdown structure is most similar to a :

A Resource breakdown structure

Version 2.0 - Août 2005 Project Scope Management 33

• Organizational process assets

• Scope statement (including deliverables)

• Approved change requests

Version 2.0 - Août 2005 Project Scope Management 34

• Work Breakdown Structure templates

Read PMI Practice Standard for WBS

Version 2.0 - Août 2005 Project Scope Management 36

And Now… Communicate !

Version 2.0 - Août 2005 Project Scope Management 37

See detailed figure PMBOK p. 106