Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 26

Project Scope

Management
Introduction

 It includes the processes required to ensure that


the project includes all the work required to
complete the project successfully

 It is primarily concerned with defining and


controlling what is or is not included in the
project

2
It involves
 A. Scope Planning
 Developing a written scope statement
 B. Scope Definition
 Subdividing the major project deliverables into smaller, more
manageable components
 C. Create WBS
 Subdividing the major project deliverables into smaller, more
manageable components
 D. Scope Verification
 Formalizing acceptance of the project scope
 E. Scope Change Control
 Controlling changes to the project scope

3
What is ‘Scope’ ?
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

Completion of the project scope is measured


against the project plan, whereas, completion of
the product scope is measured against the product
requirements

4
A. Scope Planning

 It is the process of progressively elaborating and


documenting the project work that produces the
product of the project
 Defining and managing the project scope
influences the project’s overall success

5
Inputs

 Enterprise environmental factors


 Organizational process assets
 Project charter
 Preliminary project scope statement

6
Tools and techniques

 Expert judgment

 Templates, forms and standards

7
Outputs

 Project Scope management plan


 It includes the process to
 Prepare a detailed project scope statement
 Enable the creation of WBS
 To satisfy how formal verification and acceptance of the
complete project deliverables will be obtained
 To control how requests to the detailed project scope
statement will be processed

8
B. Scope Definition
 It involves subdividing the major project
deliverables (as identified in the scope
statement), into smaller, more manageable
components to
 Improve the accuracy of cost, duration and resource
estimates
 Define a baseline for performance measurement and
control
 Facilitate clear responsibility assignments
 Proper scope definition is critical to project
success

9
Inputs

 Organizational process assets


 Project charter
 Preliminary project scope statement
 Project scope management plan
 Approved change requests

10
Tools and techniques

 Product analysis

 Alternatives identification

 Expert judgment

 Stakeholders analysis

11
Outputs

 Project scope statement

 Requested changes

 Project scope management plan (updated)

12
Project scope statement
 It includes
 Project objectives
 Product scope description
 Project requirements
 Project boundaries
 Project deliverables
 Product acceptance criteria
 Project constraints
 Project assumptions
 Initial project organizations
 Initial defined risks
 Schedule milestone
 Fund limitation
 Cost estimates
 Project configuration management requirements
 Project specifications
 Approval requirements
13
C. Create WBS

 It is a deliverable oriented hierarchical


decomposition of the work to be executed by the
project team, to accomplish the project
objectives and create the required deliverables
 The WBS represents the work specified in the
current approved project scope statement

14
Inputs

 Organizational process assets

 Project scope statement

 Project scope management plan

 Approved change requests

15
Tools and techniques

 Work breakdown structure template

 decomposition

16
Outputs

 Project scope statement (updated)


 Work breakdown structure
 WBD dictionary
 Scope baseline
 Project scope management plan (updated)
 Requested changes

17
D. Scope Verification

 It is the process of obtaining formal acceptance


of the project scope by the stakeholders.
 It requires reviewing deliverables and work
results to ensure that all were completed
correctly and satisfactorily
 If the project is terminated early, the scope
verification process should establish and
document the level and extent of completion

18
Inputs

 Project scope statement

 WBS dictionary

 Project scope management plan

 deliverables

19
Tools and techniques

 Inspections / reviews

20
Outputs

 Accepted deliverables

 Requested changes

 Recommended corrective actions

21
E. Scope Control

 It is concerned with

 Influencing the factors that create scope changes to


ensure that changes are agreed upon

 Determining that a scope change has occurred

 Managing the actual changes when and if they occur

22
Inputs

 Project scope statement


 WBS
 WBS dictionary
 Project scope management plan
 Performance reports
 Approved change requests
 Work performance information

23
Tools and techniques

 Change control system

 Variance analysis

 Re-planning

 Configuration management system

24
Outputs

 Project scope statement (updated)


 WBS (updated)
 WBS dictionary (updated)
 Scope baseline (updated)
 Requested changes
 Recommended corrective actions
 Organizational process assets (updated)
 Project management plan (updated)

25
Questions ???

26

You might also like