The document outlines the concept of project scope management, emphasizing the processes necessary to define, control, and verify project scope to ensure successful completion. It details methods for scope planning, definition, and control, including the use of expert judgment, templates, and stakeholder analysis. Additionally, the document discusses the creation of a Work Breakdown Structure (WBS) and the significance of scope verification and control in managing project boundaries, deliverables, and change requests.

1. •1

2. Concept of Project Scope
Management
It represents the management of the
process required to ensure that the
project would be completed
successfully and it is primarily
concerned with defining and
controlling what is and is not
included in the project.

3. Scope Planning
It includes:
 How project scope will be defined
 How detailed project scope statement
will be developed
 How work breakdown structure will
be created
•9/24/201
9
•3

4.  How scope verification will be
performed
 How project scope control will be
done.
•9/24/201
9
•4

5. Tool and Techniques of Scope
Planning
i. Expert Judgment: Experts make
decisions based on experiences of
equivalent projects.
ii. Templates, Form, Standards: It may
include templates for work
breakdown structure, scope
management plan, and project
scope change control.
•9/24/201
9
•5

6. Outputs of Scope Planning
It provides guidance on how the
project scope will be defined,
documented, verified, managed, and
controlled.
Component:
 Process to prepare a project scope
statement
•9/24/201
9
•6

7.  Process to create WBS
 Process for maintaining WBS and its
approval
 Process for verification and
acceptance of project deliverables
 Process to control changes in project
scope.
•9/24/201
9
•7

8. Scope Definition
It is concerned with development a
project scope statement in details as
the basis for future project decisions
& in this process the project is
defined with more specific
information about the project’s
stakeholder needs and expectations
as well as the assumptions and
constraints of the projects are
analyzed in details.
•9/24/201
9
•8

9. Tools and Technique of Scope Definition
i. Product Analysis: It is performed for
detailed understanding which may
include product breakdown, systems
analysis, system engineering, value
engineering, value analysis, and
functional analysis.
•9/24/201
9
•9

10. ii. Alternative Identification: It is a
technique used to generate
different approaches to perform the
work which includes techniques
like brainstorming, lateral thinking,
proof of concept (POC), prototype,
approach paper, etc.
•9/24/201
9
•10

11. iii. Expert Judgment : It provides
inputs for creating a detailed
project scope statement.
iv. Stakeholder Analysis: It is a
technique which helps to identify
the stakeholders’ influence and
their needs and expectations and
helps in selecting, prioritizing, and
quantifying the needs, wants, and
expectations in order to ascertain
the requirements.
•9/24/201
9
•11

12. Output of Scope Definition
i. Project Scope Statement : It is a
detailed description of project work
and deliverables along with project
boundaries which includes
 Project Objectives: These should be
quantifiable and measurable.
•9/24/201
9
•12

13.  Product Scope Description: It is a
progressively elaboration of product
characteristics. Project Requirement
 Project Requirement : Conditions or
capabilities that must be met or
possessed by the deliverables of the
project to satisfy a contract,
standard and/or specification as
applicable are project requirements.
•9/24/201
9
•13

14.  Project Boundaries: An explicit
description of what is included
within the project and what is
excluded. All assumptions of
stakeholders should be carefully
documented in order to define
project boundaries.
•9/24/201
9
•14

15.  Project Deliverables : Outputs of the
project work that comprise the
product, service or result of the
project are product deliverables. It
may include ancillary results, like
project reports and documentation.
•9/24/201
9
•15

16.  Project Acceptance Criteria : Process
and criteria for accepting completed
deliverables.
 Project Constraints : Specific project
constraints associated with the
project scope that limit the team’s
options, like predefined budget,
imposed dates and contractual
provisions.
•9/24/201
9
•16

17.  Project Assumptions: Specific project
assumptions associate the project
scope. It may describe potential
impact of those assumptions if they
prove to be invalid.
 Initial Project Organization: The
project organization with the details
of project team and stakeholders
make up this category.
•9/24/201
9
•17

18.  Initial Defined Risks: Known risks,
high attrition, quality resources
availability, technical complexity,
lack of mature process capability,
etc.
 Schedule Milestone : Milestones are
decided by the customer or
performing organization. These
imposed dates become schedule
constraints.
•9/24/201
9
•18

19.  Fund Limitation: Limitation on fund
availability, including the time-
frame.
 Cost Estimate: Cost estimate for the
project.
 Project Configurations Management
Requirements: Configuration
management and change control
requirements for the project.
•9/24/201
9
•19

20.  Approval Requirement: Identifies
approval requirements that can be
applied to items, such as project
objectives, deliverables, document
and work.
•9/24/201
9
•20

21. ii. Requested Change : In the process
of developing project scope
statement, changes may be
requested in the project
management plan and its subsidiary
plans. Integrated change control
process is executed upon all change
requests.
•9/24/201
9
•21

22.  Project Scope Management Plan
(Updates): Depending on approved
change requests originated in Scope
Definition process, the project scope
management plan needs to be
updated.
•9/24/201
9
•22

23. Creating Work Breakdown
Structure
It is a deliverable-oriented
hierarchical decomposition of the
work to be performed by the project
team to create deliverables.
•9/24/201
9
•23

24. Tools and Techniques for creating
WBS
i. Work Breakdown Structure
Templates : It provides a project
specific structure for
decomposition. As long as the
projects are similar, these
templates may be created with
inputs for previous projects.
•9/24/201
9
•24

25. ii. Decomposition : It indicates to
breakdown project deliverables into
smaller, more manageable
components is called
decomposition & should not be
done until the cost and schedule for
the work can be reliably estimated.
•9/24/201
9
•25

26. Steps to Create WBS
i. Identify final project products
necessary for achieving project
success.
ii. Identify the major deliverables
necessary for project success.
iii. Decompose until management
requirements for managing and
controlling the project are met.
•9/24/201
9
•26

27. iv. Review and refine the WBS until the
stakeholders agree with the level of
project planning, reporting and
deliveries.
•9/24/201
9
•27

28. Outputs of WBS
i. Project Scope Statement (Updates)
:The project scope statement is
updated to include changes occurring
due to approved changes if those
requests are results of the Create WBS
process.
•9/24/201
9
•28

29. ii. Work Breakdown Structure: WBS is
generated by creating WBS process
which includes WBS component,
including work package and control
accounts within a WBS.
•9/24/201
9
•29

30. iii. Work Breakdown Dictionary: It
contains the list of all WBS along
with the details on the component
associated with the WBS node.
•9/24/201
9
•30

31. Scope Verification
It is the process of completed project
scope and deliverables by
stakeholders which includes
performing review and getting formal
acceptance from stakeholders. Scope
verification process is different from
quality control process as in scope
verification is concerned with the
deliverables and work as per project
scope while the quality control
process focuses on meeting the
quality requirements specified for
the deliverables.
•9/24/201
9
•31

32. Tools and Techniques of Scope
Verification
Inspection is a process of review and
may include measuring, examining,
and verifying the deliverable against
project scope statement to determine
whether work and deliverables meet
requirements and product
acceptance criteria.
•9/24/201
9
•32

33. Outputs of Scope Verification
i. Accepted Deliverables: Deliverables
which are accepted after inspection
and necessary documentation is
prepared. Rejected deliverables are
also documents with the reasons for
non-acceptance.
•9/24/201
9
•33

34. ii. Requested Changes: Changes may
be requested during inspection and
reviews in Scope Verification
process. These change requests are
submitted for review and approval
through the integrated change
control process.
•9/24/201
9
•34

35. iii. Recommended Corrective Actions:
Customer, project team, top
management or the techno-
commercial team may request
changes which in turn, may
generate certain corrective actions
to the deliverables.
•9/24/201
9
•35

36. Scope Control
It controls the factors which
induce changes in project scope as
well as the impact of those changes
on project scope.
•9/24/201
9
•36

37. Tools and Techniques of Scope
Control
i. Change Control System : It provides
the procedures by which the project
scope and product scope can be
changed which includes the
documentation, tracking systems,
and approval levels necessary for
authorizing changes.
•9/24/201
9
•37

38. ii. Variance Analysis: It provides
project performance measurements
to assess the variation of actual
values against the planned values.
It helps in determining the
quantifiable impact of change.
•9/24/201
9
•38

39. iii. Re-planning : Approved changes
requests which affect the project
scope may necessitate the changes
to:
 WBS &WBS dictionary
 Project scope statement
 Project scope management plan
•9/24/201
9
•39

40. iv. Configuration Management System:
It is a sub system of the overall
project Management Information
System which includes the process
for submitting proposed changes,
tracking system for reviewing and
approving proposed changes,
defining approval levels for
authorizing changes, and providing
a method to validate approved
changes.
•9/24/201
9
•40

41. Output of Scope control
 Project Scope Statement (Updates):
Updates the project scope depending
on the approved change requests if
needed.
 Work Breakdown Structure (Updates):
Updates the WBS depending on the
approved change request if needed.
•9/24/201
9
•41

42.  WBS dictionary (Updates): Updates
WBS dictionary depending on the
approved change requests if needed.
 Scope Baseline (Updates): Based on
the approved change request, the
original baseline will get updated and
a new baseline is created.
•9/24/201
9
•42

43.  Requested Changes: The results of
the project scope control generates
the request changes which are
processed for review and disposition
according to the project Integrated
Change Control Process.
•9/24/201
9
•43

44.  Recommended Corrective Action:
Customer, project team, top
management or the techno
commercial team may request
changes which in turn may generate
certain correctives to the
deliverables.
•9/24/201
9
•44

45.  Updates the Organizational Process
Assets: Organizational Process Assets
are updated with causes of variances,
reasoning behind the selected
corrected action and lessons learned
from project Scope Change control.
 Updates the Project Management
Plan: Updates project management
plan, if the approved change requests
have an affect on the project scope.
•9/24/201
9
•45

46. Product Scope vs Project Scope
 Product Scope: The features and
functions that characterize a
product, service, or result
 Project Scope: The work that needs
to be accomplished to deliver a
product, service, or result with the
specified features and functions.
•9/24/201
9
•46