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
Quality
COST
SCOPE

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
Estimating
Staffing
WBS
Risk
Network Diagrams

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
Control

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

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 Inputs Tools & Techniques Outputs Project Charter
Expert judgement
Product analysis
Alternatives identification
Facilitated workshops
Outputs
Project Scope Statement
Requirements documentation
Project Document Updates
Organizational Process Assets
Collect
Requirements
Define
Scope
Create WBS
Verify
Control

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 Outputs Inputs Tools & Techniques Project scope statement
Decomposition
Work Breakdown Structure (WBS)
Requirements documentation
Organizational process assets
WBS Dictionary
Scope Baseline
Project Document Updates
Collect
Requirements
Define
Scope
Create WBS
Verify
Control

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. WBS Dictionary Supports WBS with supplemental information
NOT a Work Package (not enough detail)

14. Verify Scope Tools & Techniques Inputs Outputs Project Management Plan
Inspection
Outputs
Accepted Deliverables
Requirements Documentation
Change Requests
Requirements Traceability Matrix
Project Document Updates
Validated Deliverables
Collect
Requirements
Define
Scope
Create WBS
Verify
Control

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

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

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