Project Management

Session: Project Scope Management

CONTENT – Project Scope Management

Definitions

Scope Management Process

Plan Scope Management

Collect Requirements
 Session 6 - Objectives
At the end of this session the student should be able to understand the purpose of
scope management and be able to execute the following Scope Management
processes:

• Scope Definitions
• Plan scope management
• Collect requirements
Project Scope Management –
Definitions
Definitions

PMBOK® defines Project Scope as the "The work that needs to be

accomplished to deliver a product, service, or result with the
specified features and functions.”

Project Scope Management refers to the set of processes that

ensure a project's scope is defined and mapped accurately. Scope
Management techniques allow project managers and supervisors to
allocate just the right amount of work necessary to complete a
project successfully.

Colocar en las notas la

explicación.
 Definitions
• Product scope can be defined as the
features or characteristics of a product itself.
Whether considering design, function or
component parts, the key point is
that product scope refers to the actual
tangible product.
• Project scope focuses on the various steps or
effort taken to deliver a product or service.
Project scope can include, among other
things, assembly lines, budgets, staff
training, supply chains and personnel
allocations.
Colocar
Source: en las
Villanova notas la
University
explicación.
 Definitions

• Scope Creep is also known as requirement

creep, which refers to the uncontrolled
changes in the project’s or product’s scope.

• Gold Plating Gold plating means

intentionally adding extra features or
functions to the products which were not
included in the scope statement.

Source: PM Study Circle

Colocar en las notas la

explicación.
Project Scope Management –
Scope Management Process
Scope Management processes
Scope processes’ key deliverables

Process Project Phase Key Deliverables

Develop Scope Planning Scope Management
Management Plan Plan
Collect Project Planning Project Requirements
Requirements Plan
Define Scope Planning Scope Definition

Create the WBS Planning WBS and WBS

Dictionary
Scope Validation Monitoring and Control Accepted deliverables
and Change requests
Control Scope Monitoring and Control Work Performance and
PMP updates
Project Scope Management –
Plan Scope Management
 Scope Management Plan
It describes how the scope will be defined, developed, monitored, controlled, and
verified.
The components of a scope management plan include:
• How the project scope statement should be defined.
• How requirements should be documented, approved and changed (if required).
• How the WBS and its dictionary should be created and documented.
• How project deliverables should be verified and signed off (formal acceptance) by
the responsible party.
• How changes should be managed (request, verification, approval). This process is
directly linked to the Perform Integrated Change Control process.
The scope management plan
Colocar en las notas la can be formal or informal, broadly framed or highly
detailed, based on the needs of the project.
explicación.
Project Scope Management –
Collect Requirements
 Requirement Elicitation

“The driving force of any project is the needs and expectations of the
stakeholders that are translated into requirements”.1

These requirements will contribute to define project deliverables providing

with detailed information of functional and non functional requirements.

1Shtub,Avraham and Rosenwein, Moshe. Project Management. Processes, Methodologies

and Economics 3rd Edition. Pearson Education, Inc. (2017) , Page 60

Colocar en las notas la

explicación.
 Collect requirements

• Define and document

stakeholders’ needs
• Project success depends on the
accurate collection and
management of product and
project requirements
Collect requirements Tipear el texto. No tiene
formato.

Colocar en las notas la

explicación.
 Collect requirements

Outputs:
• Requirements
documentation
• Requirements management
plan
• Stakeholders record
• Requirements traceability
matrix
 How to classify requirements
• Business requirements, describe higher-level needs of the organization,
such as business issues or opportunities, and reasons why a to do the
project
• Stakeholder requirements, describe needs of a stakeholder(s).
• Solution requirements, describe features, functions, and characteristics of
the product, service, or result that will meet the business and stakeholder
requirements.
• Functional requirements describe the behaviors of the product.
Example: processes, data, and interactions with the product.
• Nonfunctional requirements describe the environmental conditions or
qualities required for the product to be effective. Examples: reliability,
security, performance, safety, level of service, supportability,
retention/purge, etc.
Colocar en las notas la
explicación.
 How to classify requirements

• Transition requirements describe temporary capabilities, such as data

conversion and training requirements, needed to transition from the
current “as-is” state to the future “to-be” state.
• Project requirements, which describe the actions, processes, or other
conditions the project needs to meet.
• Quality requirements, which capture any condition or criteria needed to
validate the successful completion of a project deliverable or fulfillment
of other project requirements.

Colocar en las notas la

explicación.
 CONCLUSIONS

01 Scope Management techniques allow project managers and supervisors to allocate just the
right amount of work necessary to complete a project successfully.
There are 6 processes within this knowledge area: Plan Scope, Collect Requirements, Define
02 Scope, Create Work Breakdown Structure, Verify Scope, Control Scope.
The first four listed processes belong to the planning process group and the last two belong to
the monitoring&control process group.

03 The Collect Requirements process is related to defining and documenting stakeholders’

needs.
Project success depends on the accurate collection and management of product and
Requirements may be classified using different categories:
project requirements.
04 • Business requirements
• Stakeholder requirements
• Solution requirements
• Transition requirements
• Project requirements
• Quality requirements
 REFERENCES

 PMBOK Guide v5 - A Guide to the Project Management Body of Knowledge

 Chapter 5
Thank you