The document discusses 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. Scope management is important because schedule and budget cannot be managed if scope is uncontrolled. There are five key processes for managing scope: collect requirements, define scope, create a work breakdown structure (WBS), verify scope, and control scope. The WBS is a graphical representation of all work packages that breaks the project deliverables into manageable components. Scope change management involves documentation, tracking, and approval processes for any changes to product or project scope.

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

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?
Five processes
 Collect Requirements
 Define Scope
 Create WBS
 Verify Scope
 Control Scope
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope

6. Collect Requirements
Project Charter Interviews
Focus groups
Facilitated workshops
Group creativity techniques
Group decision making techniques
Questionnaires and surveys
Observations
Prototypes
Inputs Outputs
Tools & Techniques
Requirements docs
Stakeholder
Register
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope
Requirements mgmt
plan
Requirements
traceability matrix

7. Collect Requirements
Determine product of the project
requirements
Make sure all requirements support the
business need of the project as
described in the charter

8. Define Scope
Organizational
Process Assets
Project Charter
Expert judgement
 Product analysis
Alternatives identification
Facilitated workshops
Inputs Tools & Techniques
Project Document
Updates
Outputs
Project Scope
Statement
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope
Requirements
documentation

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?

10. Create WBS
Project scope
statement
Requirements
documentation
Organizational
process assets
Decomposition
Inputs Tools & Techniques
Work Breakdown
Structure (WBS)
WBS Dictionary
Outputs
Scope Baseline
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
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. Verify Scope
Project
Management Plan
Requirements
Documentation
Requirements
Traceability Matrix
Inspection
Inputs
Tools & Techniques
Accepted
Deliverables
Validated
Deliverables
Change Requests
Outputs
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope

14. Control Scope
Project
Management Plan
Work Performance
Information
Requirements
Documentation
Variance analysis
Inputs
Tools & Techniques
Requirements
Traceability Matrix
Work Performance
Measures
Outputs
Organizational
Process Assets
Organizational
Process Assets
Change Requests
Project Management
Plan Updates
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Verify
Scope
Control
Scope

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

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