Scribd
Upload
101 views

Project Scope Management Final

The document discusses the key processes used to define and manage the scope of a project: collect requirements, define scope, create a work breakdown structure (WBS), verify scope, and control scope. Each process is defined in 1-3 sentences and its inputs, tools/techniques, and outputs are listed. The document provides an overview of how these scope management processes are used to identify all required work to successfully complete a project.

Uploaded by

Abdullah Sahi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
101 views

Project Scope Management Final

The document discusses the key processes used to define and manage the scope of a project: collect requirements, define scope, create a work breakdown structure (WBS), verify scope, and control scope. Each process is defined in 1-3 sentences and its inputs, tools/techniques, and outputs are listed. The document provides an overview of how these scope management processes are used to identify all required work to successfully complete a project.

Uploaded by

Abdullah Sahi
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

By Abdullah Sahi

M.Phil(LSBU,UK)

Visiting Faculty member of Hailey


college of commerce ,
Punjab University
Lecturer
University of Lahore

1
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
Initiation Planning Executing Controlling

5.2 Define
Scope
5.4 Verify 5.5 Control
5.1 Collect
Scope Scope
Requiremen
ts
5.3 Create
WBS

3
 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
Inputs Tools And Techniques Output

1.Project 1. Interviews 1.Requirements


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

5
6
 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
Inputs Tools And Techniques Output

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


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

8
9
 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.

1
0
Inputs Tools And Output
Techniques
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

1
1
1
2
 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.

1
3
Inputs Tools And Output
Techniques
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

1
4
1
5
 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 loss/steal.

1
6
Inputs Tools And Output
Techniques
1. Project management plan 1. Variance 1. Accepted
2. Work performance analysis deliverables
information 2. Change requests
3. Requirements 3. Project document
documentation updates
4. Requirements traceability
matrix
5. Organizational process
assets

1
7
1
8

You might also like