5 .

Scope Management
Scope Management includes the
processes required to ensure that the
project includes all the work required,
and only the work required, to
complete the project successfully.
5.1
5.2
5.3
5.4
5.5
5.6

Plan Scope Management

Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope

5 . Scope Management
Product Scope : The features and functions
that characterize a product, Service or
Result. Completion of the product scope is
measured against the product requirements.
Project Scope : The work that needs to be
accomplished to deliver a product, service
or result with the specified features and
functions. Completion of the project scope
is
measured
against
the
Project
Management Plan.

5 . Scope Management
Plan Scope Management:
Plan Scope Management is the process of
creating a scope management plan that
documents how the project scope will be
defined, validated, and controlled.
The key benefit of this process is that it
provides guidance and direction on how scope
will be managed throughout the project.
This plan helps reduce the risk of project
scope creep.

5 . Scope
Management
Plan Scope Management :

5 . Scope Management
Plan Scope Management
Inputs:
Project Management Plan
Project Charter
Enterprise Environmental Factors
Organizational Process Assets

5 . Scope Management
Tools and Techniques:
Expert Judgment
input received from knowledgeable and experienced parties
Any group or person with specialized education, knowledge,
skill, experience, or training in developing Scope
Management Plans

Meetings
Project teams may attend project meetings to develop the
scope management plan.
include the project manager, the project sponsor, selected
project team members, selected stakeholders, anyone with
responsibility for any of the scope management processes,
and others as needed.

5 . Scope Management
Outputs:

Scope Management Plan

Process for preparing a detailed project scope statement

Process that enables the creation of the WBS from the detailed project scope
statement
Process that establishes how the WBS will be maintained and approved
Process that specifies how formal acceptance of the completed project
deliverables will be obtained
Process to control how requests for changes to the detailed project scope
statement will be processed

Requirements Management Plan

How requirements activities will be planned, tracked, and reported

Configuration management activities such as: how changes to the product will
be initiated, how impacts will be analyzed, how they will be traced, tracked,
and reported, as well as the authorization levels required to approve these
changes
Requirements prioritization process
Product metrics that will be used and the rationale for using them
Traceability structure to reflect which requirement attributes will be captured on
the traceability matrix

5 . Scope Management
Collect Requirements :
The process of determining, documenting and managing
stakeholders needs to meet the project objectives . Collecting
requirements is defining and managing customer expectations.

The projects success is directly influenced by the care taken

in
capturing
and
managing
project
and
product
requirements.
Requirements include quantified and documented needs
and expectations of the Sponsor, Customer, and other
Stakeholders.
Requirements become the foundation of WBS. Cost,
Schedule, and Quality Planning are built up on these
requirements.

5 . Scope
Management
Collect Requirements :

5 . Scope Management
Collect Requirements
Inputs:
Scope Management Plan
Requirements Management Plan
Stakeholder Management Plan
Project Charter
Stakeholder Register

5 . Scope Management
Tools and Techniques:

Interviews

Formal or Informal Approach

Prepared and Spontaneous Questions
Record the Responses
One-on-One, Multiple Interviewers or Interviewees

Focus Groups
Bring Prequalified Stakeholders and SMEs together
Trained Moderator
More Conversational

Facilitated Workshops

Bring Key Cross Functional Stakeholders together

Quickly define the cross functional requirements
Quickly reconcile the stakeholder differences
Increased stakeholders consensus
Examples JAD, QFD

5 . Scope Management
Tools and Techniques:

Group Creativity Techniques

Brainstorming
Nominal Group Technique (Brainstorming with voting process)
Delphi Technique (Experts answers questions. Responses are
available to only facilitator)
Idea/Mind mapping (to reflect the commonality and differences in
understanding the requirements)
Affinity Diagram (large number of ideas to be sorted in to groups
for review and analysis)
Multicriteria decision analysis. A technique that utilizes a decision
matrix to provide a systematic analytical approach for establishing
criteria, such as risk levels, uncertainty, and valuation, to evaluate
and rank many ideas.

Group Decision Making Techniques

Unanimity
Majority
Plurality
Dictatorship

5 . Scope Management
Tools and Techniques:
Questionnaires and Surveys
To quickly accumulate the information from wide number of
respondents
Used when there is Broad Audience, Quick Turnaround is needed,
Statistical Analysis is appropriate

Observations
Used when the stakeholder has the difficulty or reluctant to
articulate the requirements.
Job Shadowing
Participant Observer

Prototype
Used to get the early feedback on requirements by providing a
working model of the expected product
This support the concept of progressive elaboration.

5 . Scope Management
Tools and Techniques:

Benchmarking

Context Diagrams

Benchmarking involves comparing actual or planned practices, such as

processes and operations, to those of comparable organizations to identify
best practices, generate ideas for improvement, and provide a basis for
measuring performance.
The organizations compared during benchmarking can be internal or external.
The context diagram is an example of a scope model.
Context diagrams visually depict the product scope by showing a business
system and how people and other systems (actors) interact with it.
Context diagrams show inputs to the business system, the actor(s) providing
the input, the outputs from the business system, and the actor(s) receiving the
output.

Document Analysis

Document analysis is used to elicit requirements by analyzing existing

documentation and identifying information relevant to the requirements.
Examples: Business Plans, agreements, requests for proposal, current process
flows, logical data models, business rules repositories, application software
documentation, business process or interface documentation, use cases etc.

5 . Scope Management
Outputs:
Requirements Documentation
Describes how individual requirements meet
the business need for the project
Starts at higher level and progressively
elaborated
Requirements
must
be
unambiguous
(measurable
and
testable),
traceable,
consistent and acceptable to key stakeholders

Requirements Traceability Matrix

This is a grid that links product requirements
from their origin to the deliverables that
satisfy them.
It provides a means to track requirements
throughout the project life cycle.

5 . Scope Management

5 . Scope Management
Define Scope :
The process of developing a detailed description of the
product and the project.
The key benefit of this process is that it describes the project,
service, or result boundaries by defining which of the
requirements collected will be included in and excluded from
the project scope.

5 . Scope
Management

Define Scope :

5 . Scope Management
Define Scope
Inputs:
Scope Management Plan
Project Charter
Requirements Documentation
Organization Process Assets

5 . Scope Management
Tools and Techniques:
Expert Judgment
Product Analysis
This is used when Product as a deliverable
It is Application Area dependant
Product Breakdown, System Analysis, Requirements
Analysis, Systems Engineering, Value Engineering
and Value Analysis.

Alternatives Generation
Alternatives generation is a technique used to develop as
many potential options as possible in order to identify
different approaches to execute and perform the work of
the project.
Brainstorming, Lateral Thinking, etc

Facilitated Workshops

5 . Scope Management
Define Scope Outputs:

Project Scope Statement

Product scope description - Progressively elaborates the
characteristics of the product, service, or result described in the
project charter and requirements documentation
Acceptance Criteria - A set of conditions that is required to be
met before deliverables are accepted
Deliverable - 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.
Project Exclusion - Identifies what is excluded from the project
Constraints - A limiting factor that affects the execution of a
project or process.
Assumptions - A factor in the planning process that is
considered to be true, real, or certain, without proof or
demonstration.

Project Document Updates

5 . Scope Management
Create WBS :
The process of subdividing project
deliverables and project work in to
smaller
and
more
manageable
components.
It is a deliverable oriented hierarchical
decomposition
Each descending level represents an
increasingly detailed definition of the
project work.
WBS organizes and defines the total
scope of the project.

5 . Scope
Management
Create WBS :

5 . Scope Management
Create WBS
Inputs:
Scope Management Plan
Project Scope Statement
Requirements Documentation
Enterprise Environmental Factors
Organization Process Assets

5 . Scope Management
Tools and Techniques:
Decomposition
Subdivision of the project deliverables in to
smaller, more manageable components.
Work Package level is the lowest level at which
cost and activity duration can be easily
estimated and managed
Rolling Wave Planning
100% rule

Expert Judgment

5 . Scope Management
Create WBS Outputs:
Scope Baseline
It is a component of PMP
Project Scope Statement + WBS +
WBS Dictionary

Project Document Updates

5 . Scope Management
Validate Scope:
The
process
of
formalizing
the
acceptance of the completed project
deliverables.
It includes reviewing deliverables with
customer or sponsor to ensure that they
are
completed
satisfactorily
and
obtaining formal acceptance of the
deliverables
Scope Validation differs from Quality
Control

5 . Scope
Management

Validate Scope :

5 . Scope Management
Verify Scope
Inputs:

PMP
Requirements Documentation
RTM
Verified Deliverables
Work Performance Data - Work performance data can
include the degree of compliance with requirements,
number
of
nonconformities,
severity
of
the
nonconformities, or the number of validation cycles
performed in a period of time.

5 . Scope Management
Tools and Techniques:
Inspection
Includes
activities
such
as
measuring,
examining,
and
verifying
to
determine
whether the work and the deliverables meet
requirements and product acceptance criteria.
Sometimes called as reviews, audits and
walkthroughs.

Group Decision Making Techniques - These

techniques are used to reach a conclusion when
the validation is performed by the project team
and other stakeholders

5 . Scope Management
Verify Scope Outputs:
Accepted Deliverables
Deliverables
that
meet
the
acceptance criteria are formally
signed off and approved by the
customer or sponsor.

Change Requests
Work Performance Information
Project Document Updates

5 . Scope Management
Control Scope:
The process of monitoring the status of
the project and product scope and
managing changes to the scope baseline
It
ensures
all
the
recommended
corrective or preventive actions are
processed
through
the
Integrated
Change Control Process.
Uncontrolled changes are often referred
as Scope Creep.

5 . Scope
Management

Control Scope :

5 . Scope Management
Control Scope
Inputs:
PMP
Requirements Documentation
RTM
Work Performance Data
Information about project progress

OPA

5 . Scope Management
Tools and Techniques:
Variance Analysis
Variance analysis is a technique for
determining the cause and degree of
difference between the baseline
and actual performance.
Depending of the magnitude of the
variation, a corrective or preventive
action is decided.

5 . Scope Management
Control Scope Outputs:
Work Performance Information
Planned vs. Actual

Change Requests
PMP Updates
Project Document Updates
OPA Updates

5 . Scope Management
Lets Practice