28-Jan-21
ABDUL QAYOOM
B.E (CIVIL)
M.E (CONSTRUCTION MANAGEMENT)
PhD Candidate (CONSTRUCTION ENGINEERING & INFRASTRUCTURE MANAGEMENT)
© Abdul Qayoom
PROJECT SCOPE
MANAGEMENT
© Abdul Qayoom
1
28-Jan-21
4 PROJECT SCOPE MANAGEMENT
CONTENTS
Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope
© Abdul Qayoom
2
28-Jan-21
5 PROJECT SCOPE MANAGEMENT
Scope Management Plan
The scope management plan is a component of the project management plan
that describes how the scope will be defined, developed, monitored, controlled,
and validated.
The components of a scope management plan include:
Process for preparing a project scope statement;
Process that enables the creation of the WBS from the detailed project scope
statement;
Process that establishes how the scope baseline will be approved and
maintained; and
Process that specifies how formal acceptance of the completed project
deliverables will be obtained. © Abdul Qayoom
6 PROJECT SCOPE MANAGEMENT
Requirements Management Plan
Collect Requirements is the process of determining, documenting, and managing
stakeholder needs and requirements to meet objectives.
The key benefit of this process is that it provides the basis for defining the project
scope.
© Abdul Qayoom
3
28-Jan-21
7 PROJECT SCOPE MANAGEMENT
Define Scope
Define Scope is the process of developing a detailed description of the project
and product.
The key benefit of this process is that it describes the product, service, or result
boundaries and acceptance criteria.
Define Scope process selects the final project requirements from the requirements
documentation developed during the Collect Requirements process. It then
develops a detailed description of the project and product, service, or result.
© Abdul Qayoom
8 PROJECT SCOPE MANAGEMENT
Define Scope
The preparation of a detailed project scope statement builds upon the major
deliverables, assumptions, and constraints that are documented during project
initiation.
During project planning, the project scope is defined and described with greater
specificity as more information about the project is known.
Existing risks, assumptions, and constraints are analyzed for completeness and
added or updated as necessary.
The Define Scope process can be highly iterative. In iterative life cycle projects, a
high-level vision will be developed for the overall project, but the detailed scope
is determined one iteration at a time
© Abdul Qayoom
4
28-Jan-21
9 PROJECT SCOPE MANAGEMENT
Project Scope Statement
The project scope statement is the description of the project scope, major
deliverables, assumptions, and constraints.
The project scope statement documents the entire scope, including project and
product scope.
It describes the project’s deliverables in detail. It also provides a common
understanding of the project scope among project stakeholders.
It may contain explicit scope exclusions that can assist in managing stakeholder
expectations.
© Abdul Qayoom
10 PROJECT SCOPE MANAGEMENT
Project Scope Statement
It enables the project team to perform more detailed planning, guides the project
team’s work during execution, and provides the baseline for evaluating whether
requests for changes or additional work are contained within or outside the
project’s boundaries.
The degree and level of detail to which the project scope statement defines the
work that will be performed and the work that is excluded can help determine
how well the project management team can control the overall project scope.
© Abdul Qayoom
10
5
28-Jan-21
11 PROJECT SCOPE MANAGEMENT
Project Scope Statement
The detailed project scope statement, either directly or by reference to other
documents, includes the following:
Product scope description
Progressively elaborates the characteristics of the product, service, or result
described in the project charter and requirements documentation.
Deliverables
Any unique and verifiable product, result, or capability to perform a service that is
required to be produced to complete a process, phase, or project. Deliverables also
include auxiliary results, such as project management reports and documentation.
These deliverables may be described at a summary level or in great detail.
© Abdul Qayoom
11
12 PROJECT SCOPE MANAGEMENT
Project Scope Statement
Acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
Project exclusions
Identifies what is excluded from the project. Explicitly stating what is out of scope for
the project helps manage stakeholders’ expectations and can reduce scope creep.
© Abdul Qayoom
12
6
28-Jan-21
13 PROJECT SCOPE MANAGEMENT
Difference between Project Charter and Project Scope Statement
Although the project charter and the project scope statement are sometimes
perceived as containing a certain degree of redundancy, they are different in the
level of detail contained in each.
The project charter contains high level information, while the project scope
statement contains a detailed description of the scope components. These
components are progressively elaborated throughout the project.
© Abdul Qayoom
13
14 PROJECT SCOPE MANAGEMENT
Difference between Project Charter and Project Scope Statement
© Abdul Qayoom
14
7
28-Jan-21
15 PROJECT SCOPE MANAGEMENT
Create WBS
Create WBS is the process of subdividing project deliverables and project work
into smaller, more manageable components.
The key benefit of this process is that it provides a framework of what has to be
delivered.
© Abdul Qayoom
15
16 PROJECT SCOPE MANAGEMENT
Create WBS
The WBS is a hierarchical decomposition of the total scope of work to be carried
out by the project team to accomplish the project objectives and create the
required deliverables.
The WBS organizes and defines the total scope of the project and represents the
work specified in the current approved project scope statement.
The planned work is contained within the lowest level of WBS components, which
are called work packages.
A work package can be used to group the activities where work is scheduled
and estimated, monitored, and controlled.
In the context of the WBS, work refers to work products or deliverables that are the
result of activity and not to the activity itself. © Abdul Qayoom
16
8
28-Jan-21
17 PROJECT SCOPE MANAGEMENT
Tools and Techniques to Create WBS
Decomposition
Decomposition is a technique used for dividing and subdividing the project
scope and project deliverables into smaller, more manageable parts.
The work package is the work defined at the lowest level of the WBS for which
cost and duration can be estimated and managed.
The level of decomposition is often guided by the degree of control needed to
effectively manage the project.
The level of detail for work packages will vary with the size and complexity of the
project.
© Abdul Qayoom
17
18 PROJECT SCOPE MANAGEMENT
Tools and Techniques to Create WBS
Decomposition
Decomposition of the total project work into work packages generally involves
the following activities:
Identifying and analyzing the deliverables and related work,
Structuring and organizing the WBS,
Decomposing the upper WBS levels into lower-level detailed components,
Developing and assigning identification codes to the WBS components
Verifying that the degree of decomposition of the deliverables is
appropriate
© Abdul Qayoom
18
9
28-Jan-21
19 PROJECT SCOPE MANAGEMENT
Tools and Techniques to Create WBS
Decomposition
WBS structure may be created through various approaches. Some of the popular
methods include the top-down approach, the use of organization-specific
guidelines, and the use of WBS templates. A bottom-up approach can be used to
group subcomponents.
The WBS structure can be represented in a number of forms, such as:
Using phases of the project life cycle as the second level of decomposition, with
the product and project deliverables inserted at the third level
Using major deliverables as the second level of decomposition
© Abdul Qayoom
19
20 PROJECT SCOPE MANAGEMENT
Tools and Techniques to Create WBS
Decomposition
Incorporating subcomponents that may be developed by organizations outside
the project team, such as contracted work.
The seller then develops the supporting contract WBS as part of the contracted
work.
The WBS represents all product and project work, including the project
management work. The total of the work at the lowest levels should roll up to the
higher levels so that nothing is left out and no extra work is performed. This is
sometimes called the 100 percent rule
© Abdul Qayoom
20
10
28-Jan-21
21 PROJECT SCOPE MANAGEMENT
WBS Example
© Abdul Qayoom
21
22 PROJECT SCOPE MANAGEMENT
Create WBS: Output : Scope Baseline
The scope baseline is the approved version of a scope statement, WBS, and its
associated WBS dictionary, which can be changed only through formal change
control procedures and is used as a basis for comparison.
It is a component of the project management plan.
Components of the scope baseline include:
Project scope statement: The project scope statement includes the
description of the project scope, major deliverables, assumptions, and
constraints
WBS: The WBS is a hierarchical decomposition of the total scope of work to
be carried out by the project team to accomplish the project objectives
and create the required deliverables. © Abdul Qayoom
22
11
28-Jan-21
23 PROJECT SCOPE MANAGEMENT
Create WBS: Output : Scope Baseline
Work package: The lowest level of the WBS is a work package with a unique
identifier. These identifiers provide a structure for hierarchical summation of costs,
schedule, and resource information and form a code of accounts.
Planning package: A planning package is a work breakdown structure
component below the control account and above the work package with known
work content but without detailed schedule activities.
WBS dictionary: The WBS dictionary is a document that provides detailed
deliverable, activity, and scheduling information about each component in the
WBS. The WBS dictionary is a document that supports the WBS.
© Abdul Qayoom
23
24 PROJECT SCOPE MANAGEMENT
Create WBS: Output : Scope Baseline
Most of the information included in the WBS dictionary is created by other
processes and added to this document at a later stage.
Information in the WBS dictionary may include but is not limited to:
Code of account identifier, Resources required,
Description of work, Cost estimates,
Assumptions and constraints, Quality requirements,
Responsible organization, Acceptance criteria,
Schedule milestones Technical references, and
Associated schedule activities, Agreement information.
© Abdul Qayoom
24
12
28-Jan-21
25 PROJECT SCOPE MANAGEMENT
Validate Scope
Validate Scope is the process of formalizing acceptance of the completed project
deliverables. The key benefit of this process is that it brings objectivity to the
acceptance process and increases the probability of final product, service, or result
acceptance by validating each deliverable. © Abdul Qayoom
25
26 PROJECT SCOPE MANAGEMENT
Control Scope
Control Scope is the process of monitoring the status of the project and product
scope and managing changes to the scope baseline. The key benefit of this process
is that the scope baseline is maintained throughout the project. © Abdul Qayoom
26
13
28-Jan-21
27 QUESTIONS
© Abdul Qayoom
27
14
