Project Scope

Management
Sections of this presentation were adapted
from A Guide to the Project Management
Body of Knowledge 4th Edition, Project
Management Institute Inc., © 2009
 Project Scope Management
“The processes required to ensure that the
project includes all the work required, and
only the work required, to complete the
project successfully”

Answers the question – “What will the

project produce in the end”.
 Why Do We Manage Scope?
Can’t manage schedule
and budget if scope is
out of control (Triple
Constraint) TIME

Scope docs are used to

manage expectations
Quality

SCOPE COST
Scope Management Key Points
What is scope management
 Checking to ensure that one is completing work
 Saying No to additional work not in the charter
 Preventing extra work/gold plating
Work Breakdown Structure Estimating

(WBS)
 Foundation of the project, all
planning and controlling is based Staffing Risk
WBS
on the WBS
 Identifies all work to be
performed, if it is not in the WBS
it does not need to be done Network
Diagrams
 Graphical picture of work
 How Do We Manage Scope?
Five processes
 Collect Requirements
 Define Scope
 Create WBS
 Verify Scope
 Control Scope

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
 Collect Requirements
Inputs Tools & Techniques Outputs

Project Charter  Interviews Requirements docs

 Focus groups

Stakeholder  Facilitated workshops Requirements mgmt

Register  Group creativity techniques plan

 Group decision making techniques Requirements

traceability matrix
 Questionnaires and surveys
 Observations
 Prototypes

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
 Collect Requirements
Determine product of the project
requirements
Make sure all requirements support the
business need of the project as
described in the charter
 Define Scope
Inputs Tools & Techniques
Project Charter
 Expert judgement Outputs
Project Scope
Requirements  Product analysis Statement
documentation  Alternatives identification
Project Document
Organizational  Facilitated workshops Updates
Process Assets

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
Project Scope Statement
Product scope description
Product acceptance
criteria
Project deliverables
Project exclusions
Project constraints
Project assumptions

Remember the difference between product and project?

 Create WBS
Inputs Tools & Techniques Outputs
Project scope
statement  Decomposition
Work Breakdown
Requirements
Structure (WBS)
documentation
Organizational WBS Dictionary
process assets

Scope Baseline

Project Document
Updates

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
 Work Breakdown Structure
Start with major project deliverables or
phases
“Decomposition” is breaking down the
deliverables into more manageable parts
 Not all branches need the same level of
decomposition!
Decompose into “Work Packages”
 8-80 Hour Rule  Don’t break work down too
much
 Work Breakdown Structure

New Warehouse

Design - 1 Construction - 2 Commissioning - 3

Structural - 1.1 Concrete Install – 2.1

Steel Package 1.1.1 Steel Install – 2.2

Concrete Package 1.1.2 Drywall Install – 2.3

Architectural – 1.2 1st Floor Package 2.3.1

Floor Layout 1.2.1 2nd Floor Package 2.3.2

Elevations 1.2.2

Door Schedule 1.2.3

 Verify Scope
Tools & Techniques
Inputs
Project  Inspection
Management Plan Outputs
Accepted
Deliverables
Requirements
Documentation
Change Requests
Requirements
Traceability Matrix
Project Document
Validated Updates
Deliverables

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
 Control Scope
Tools & Techniques
Inputs Outputs
Project
Work Performance
Management Plan  Variance analysis
Measures
Work Performance Organizational
Information Process Assets
Requirements Change Requests
Documentation

Requirements Project Management

Traceability Matrix Plan Updates

Organizational Project Document

Process Assets Updates

Collect Define Create Verify Control

WBS
Requirements Scope Scope Scope
 Scope Definitions
Change Control System
 Documentation, tracking, and approvals required to
change project scope
Configuration Management System
 Documentation, tracking, and approvals required to
change product scope
Management by Objectives (MBO)
 Establish unambiguous and realistic objectives
 Periodically evaluate if objectives are being met
 Take corrective action
Other Topics – Project Selection
Benefit Measurement
Methods (Comparative
Approach)
 Murder Board – Panel
that tries to shoot down
new ideas
 Scoring Models
 Benefit Compared to
Cost
Constrained
Optimization Methods
(Mathematical)
 Linear Programming
 Integer Programming
 Multi-Objective
Programming