Scope Management

By Hosam Dahb

1 LOGO
 Scope Management
Processes used to identify all the work
required and only the work required
to successfully complete the project

• Collect Requirements
• Define Scope
• Create WBS
• Verify Scope
• Control Scope
2
5. Scope Management Processes
Initiation Planning Executing Controlling

5.2 Define
Scope

5.4 Verify 5.5 Control

5.1 Collect Scope Scope
Requirements
5.3 Create
WBS

3
 5.1 Collect Requirements
• Collect Requirements is the process of
defining and documenting stakeholders’ needs
to meet the project objectives.
• Collecting requirements is defining and
managing customer expectations.
• Requirements become the foundation of the
WBS. Cost, schedule, and quality planning are
all built upon these requirements.

4
 5.1 Collect Requirements
Inputs Tools And Techniques Output

1.Project charter 1. Interviews 1. Requirements

2.Stakeholder 2. Focus groups documentation
register 3. Facilitated workshops 2. Requirements
4. Group creativity techniques management plan
5. Group decision making 3. Requirements
techniques Traceability Matrix
6. Questionnaires and surveys
7. Observations
8. Prototypes

5
Collect Requirements Data Flow Diagram

6
 5.2 Define Scope
• Define Scope is the process of developing a
detailed description of the project and
product.
• The preparation of a detailed project scope
statement is critical to project success and
builds upon the major deliverables,
assumptions, and constraints that are
documented during project initiation.

7
 5.2 Define Scope
Inputs Tools And Techniques Output

1. Project charter 1. Expert judgment 1. Project scope

2. Requirements 2. Product analysis statement
documentation 3. Alternatives identification 2. Project document
3. Organizational 4. Facilitated workshops updates
process Assets

8
Define Scope Data Flow Diagram

9
 5.3 Create WBS
Work Breakdown Structure

• Create WBS is the process of subdividing

project deliverables and project work into
smaller, more manageable components.
• The WBS 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.

10
 5.3 Create WBS
Inputs Tools And Techniques Output

1. Project scope statement 1. Decomposition 1. WBS

2. Requirements documentation 2. WBS dictionary
3. Organizational process 3. Scope baseline
assets 4. Project document
updates

11
Create WBS Data Flow Diagram

12
 5.4 Verify Scope
• Verify Scope is the process of formalizing
acceptance of the completed project
deliverables. This includes reviewing
deliverables with the customer or sponsor to
ensure that they are completed satisfactorily
• scope verification is primarily concerned with
acceptance of the deliverables while Quality
control is primarily concerned with
correctness of the deliverables and meeting
the quality requirements specified for the
deliverables. 13
 5.4 Verify Scope
Inputs Tools And Techniques Output

1. Project management plan 1. Inspection 1. Accepted

2. Requirements documentation deliverables
3. Requirements traceability 2. Change requests
matrix 3. Project document
4. Validated deliverables updates

14
Verify Scope Data Flow Diagram

15
 5.5 Control Scope
• Control Scope is the process of monitoring the
status of the project and product scope and
managing changes to the scope baseline.
• Uncontrolled changes are often referred to as
project scope creep.

16
 5.5 Control Scope
Inputs Tools And Techniques Output

1. Project management plan 1. Variance analysis 1. Accepted

2. Work performance information deliverables
3. Requirements documentation 2. Change requests
4. Requirements traceability matrix 3. Project document
5. Organizational process assets updates

17
Control Scope Data Flow Diagram

18
 Exam Question
• List
What allisthe
theScope
scopeManagement
managementProcesses
and how the
Inputs,change
scope Tools &can
Techniques
impacts Time,
and Outputs
Quality and
and
drawconstraints?
cost all the related diagrams

19
20