This document provides an overview of project scope management. It defines scope management as ensuring a project includes all required work and only the required work to complete the project successfully. It then outlines the six key processes for managing scope: plan scope management, collect requirements, define scope, create a work breakdown structure (WBS), validate scope, and control scope. These processes involve identifying deliverables, decomposing work, and monitoring the project to ensure it stays within scope. Managing scope is important for also managing schedule and budget (the "triple constraint").

1. 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

2. 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”.
Project scope management is a process that helps in
determining and documenting the list of all the project goals,
tasks, deliverables, deadlines, and budgets as a part of the
planning process.

3. Why Do We Manage Scope?
• Can’t manage schedule and budget if
scope is out of control (Triple Constraint)
• Scope docs are used to manage
expectations
TIME
COST
SCOPE
Quality

4. 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
(WBS)
 Foundation of the project, all
planning and controlling is based
on the WBS
 Identifies all work to be
performed, if it is not in the WBS
it does not need to be done
 Graphical picture of work
WBS
Estimating
Network
Diagrams
Staffing Risk

5. How Do We Manage Scope?
• Six processes
1. Plan Scope Management
2. Collect Requirements
3. Define Scope
4. Create WBS
5. Verify Scope
6. Control Scope
Collect
Requirements
Define
Scope
Create
WBS
Control
Scope
Plan Scope
Management
Validate
Scope

6. Plan Scope Management
Project Charter Expert Judgement
Meetings
Data Analysis
Inputs Outputs
Tools & Techniques
Scope Management
Plan
Project
Management
Plan
Requirements
Management plan
Collect
Requirements
Define
Scope
Create
WBS
Validate
Scope
Control
Scope
Plan Scope
Management
Organizational
Process Assets
Enterprise
Environmental
Factors

7. Collect Requirements
Project Charter
Expert judgement
Data gathering
Data analysis
Decision making
Data representation
Interpersonal and team skills
Context diagram
Prototypes
Inputs Outputs
Tools & Techniques
Requirements
documentation
Project
management plan
Requirements
management plan
Requirements
traceability matrix
Collect
Requirements
Define
Scope
Create
WBS
Control
Scope
Plan Scope
Management
Project documents
Agreements
Enterprise
environmental
factors
Organizational
process
Validate
Scope

8. Define Scope
Organizational
Process Assets
Project Charter
 Expert judgement
 Data analysis
 Decision making
 Interpersonal and
team skills
 Product analysis
Inputs Tools & Techniques
Project Document
Updates
Outputs
Project Scope
Statement
Project
management plan
Project documents
Enterprise environmental
factors
Collect
Requirements
Define
Scope
Create
WBS
Control
Scope
Plan Scope
Management
Validate
Scope

9. Project Scope Statement
• Product scope description
• Product acceptance criteria
• Project deliverables
• Project exclusions
• Project constraints
• Project assumptions
Remember the difference between product and project?
Product scope –The features and functions that characterize a product or service
Project Scope- The work that must be done to deliver a product with the
specified features and functions

10. Create WBS
Project
management plan
Organizational
process assets
Expert judgement
Decomposition
Inputs Tools & Techniques
Work Breakdown
Structure (WBS)
Outputs
Scope Baseline
Project Document
Updates
Project documents
Enterprise environmental
factors
Collect
Requirements
Define
Scope
Create
WBS
Control
Scope
Plan Scope
Management
Validate
Scope

11. 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

12. Work Breakdown Structure
New Warehouse
Design - 1 Construction - 2 Commissioning - 3
Structural - 1.1
Architectural – 1.2
Steel Package 1.1.1
Concrete Package 1.1.2
Floor Layout 1.2.1
Elevations 1.2.2
Door Schedule 1.2.3
Concrete Install – 2.1
Steel Install – 2.2
Drywall Install – 2.3
1st Floor Package 2.3.1
2nd Floor Package 2.3.2

13. Validate Scope
Project Management Plan  Inspection
 Decision making
Inputs
Tools & Techniques
Accepted
Deliverables
Validated Deliverables
Change Requests
Outputs
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Validate
Scope
Control
Scope
Plan Scope
Management
Project documents
Work performance data
Work performance
information

14. Control Scope
Project
Management Plan
Work Performance
Information
 Data Analysis
Inputs
Tools & Techniques
Work Performance
information
Outputs
Organizational
Process Assets
Change Requests
Project Management
Plan Updates
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Control
Scope
Plan Scope
Management
Validate
Scope
Project documents