1. Project Scope Management
Sectionsof thispresentation wereadapted from A Guideto theProject
Management Body of Knowledge 5th
Edition, Project Management Institute
Inc., © 2013

2. Project ScopeManagement
“Theprocessesrequired to ensurethat theproject includesall the
work required, and only thework required, to completetheproject
successfully”
Answersthequestion – “What will theproject producein theend”.

3. Why Do WeManageScope?
Can’t managescheduleand budget if scopeis
out of control (TripleConstraint)
Scopedocsareused to manageexpectations
TIME
COSTSCOPE
Quality

4. ScopeManagement Key Points
What isscopemanagement
 Checking to ensurethat oneiscompleting work
 Saying No to additional work not in thecharter
 Preventing extrawork/gold plating
 Work Breakdown Structure(WBS)

Foundation of theproject, all
planning and controlling isbased
on theWBS

Identifiesall work to beperformed,
if it isnot in theWBSit doesnot
need to bedone

Graphical pictureof work
WBS
Estimating
Network
Diagrams
Network
Diagrams
Staffing Risk

5. How Do WeManageScope?
Fiveprocesses
1. Collect Requirements
2. DefineScope
3. CreateWBS
4. Verify Scope
5. Control Scope
Collect
Requirements
Define
Scope
Create
WBS
Validate
Scope
Control
Scope

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

7. Collect Requirements
 Determineproduct of theproject requirements
 Makesureall requirementssupport thebusinessneed of the
project asdescribed in thecharter

8. DefineScope
Project Charter
Project Charter
 Expert judgment
 Product analysis
 Alternatives generation
 Facilitated workshops
 Observations
Inputs Tools & Techniques
Requirements
traceability matrix
Outputs
Project Scope
Statement
Collect
Requirements
Define
Scope
Create
WBS
Validate
Scope
Control
Scope
Requirements
documentation
Stake Holder
Register

9. Project ScopeStatement
 Product scopedescription
 Product acceptancecriteria
 Project deliverables
 Project exclusions
 Project constraints
 Project assumptions
No tice the difference between pro duct and pro ject.

10. CreateWBS
Scopemanagement
plan
Project scopestatement
Requirements
documentation
Enterprise
environmental
factors
Organizational process
assets
Decomposition
Expert Judgment
Inputs Tools & Techniques
Work Breakdown
Structure (WBS)
WBS Dictionary
Outputs
Scope Baseline
Project Document
Updates
Collect
Requirements
Define
Scope
Create
WBS
Validate
Scope
Control
Scope

11. Work Breakdown Structure
 Start with major project deliverablesor phases
 “Decomposition” isbreaking down thedeliverablesinto more
manageableparts
 Not all branchesneed thesamelevel of decomposition!
 Decomposeinto “Work Packages”
 8-80 Hour Rule⇒ Don’t break work down too much

12. Work Breakdown Structure
New Website
Plan/Design - 1 Implement/Develop- 2 Production- 3
Front end - 1.1
Architectural – 1.2
Usability1.1.1
Graphic1.1.2
Web Hosting 1.2.1
Database 1.2.2
Security 1.2.3
Front end development– 2.1
Graphic– 2.2
Database /HostingArchitecture– 2.3
Test Environment 2.3.1
Production Environment2.3.2
Back up Environment 2.3.3

13. ValidateScope
Project
Management Plan
Requirements
Documentation
Requirements
Traceability Matrix
 Inspection
Inputs
Tools & Techniques
Validated
Deliverables
Outputs Accepted
deliverables
Change requests
Work performance
information
Project documents
updates
Collect
Requirements
Define
Scope
Create
WBS
Validate
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
Validate
Scope
Control
Scope

15. ScopeDefinitions
Change Control System
 Documentation, tracking, and approvalsrequired to
changeprojectscope
Configuration Management System
 Documentation, tracking, and approvalsrequired to
changeproductscope
Management by Objectives (MBO)
 Establish unambiguousand realistic objectives
 Periodically evaluateif objectivesarebeing met
 Takecorrectiveaction

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