Project 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 …

It provides guidance and direction on how

scope will be managed throughout the project.
The scope management plan is a component of
the project or program management plan.
This plan helps reduce the risk of project
scope creep.
Requirements Management Plan

The Requirements Management Plan is a

necessary tool for establishing how requirements
will be collected, analyzed, documented, and
managed throughout the lifecycle of a project.
 1.Collect Requirements
The Process of defining and documenting stakeholders’
needs to meet the project objectives.
Requirements include the quantified and documented
needs & expectation of the sponsor, customer, & other
Stakeholders
Requirements become the foundation of the WBS,
cost, schedule, & quality planning are all built upon
these requirements
Organizations categorize requirements into project
requirements & product requirements
 Collect Requirements
Tools and Techniques
An interview is a formal or informal approach to
elicit information from stakeholders by talking to
them directly. It is typically performed by asking
prepared and spontaneous questions and
recording the responses. Interviews are often
conducted on an individual basis between an
interviewer and an interviewee, but may involve
multiple interviewers and/or multiple
interviewees.
Focus groups bring together prequalified
stakeholders and subject matter experts to learn
about their expectations and attitudes about a
proposed product, service, or result. A trained
moderator guides the group through an
interactive discussion, designed to be more
conversational than a one‐on‐one interview.
Facilitated workshops are focused sessions that
bring key stakeholders together to define product
requirements. Workshops are considered a
primary technique for quickly defining cross‐
functional requirements and reconciling
stakeholder differences
Observations provide a direct way of viewing
individuals in their environment and how they
perform their jobs or tasks and carry out
processes.
 Group Creativity Techniques
• Brainstorming. A technique used to generate and collect
multiple ideas related to project and product requirements
• Nominal group technique. A technique that enhances
brainstorming with a voting process used to rank the most
useful ideas for further brainstorming or for prioritization.
• Idea/mind mapping. A technique in which ideas created
through individual brainstorming sessions are consolidated
into a single map to reflect commonality and differences in
understanding, and generate new ideas.
Plurality. A decision that is reached whereby
the largest block in a group decides, even if a
majority is not achieved. This method is
generally used when the number of options
nominated is more than two.
Dictatorship. is when one person makes the
decision for the whole group.
 Delphi Technique
is a way of letting everyone in the group give
their thoughts about what should be in the
product while keeping them anonymous. When
you use the Delphi technique, everybody writes
down their answers to the same questions about
what the product needs to do and then hands
them into a moderator. The questions could be
about specific features that the product should
have.
Questionnaires and surveys are written sets of
questions designed to quickly accumulate
information from a large number of respondents.
Questionnaires and/or surveys are most
appropriate with varied audiences, when a quick
turnaround is needed, when respondents are
geographically dispersed, and where statistical
analysis is appropriate.
Document analysis is used to elicit
requirements by analyzing existing
documentation and identifying information
relevant to the requirements. There are a wide
range of documents that may be analyzed to help
elicit relevant requirements
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
Prototyping is a method of obtaining early
feedback on requirements by providing a
working model of the expected product before
actually building it. Since a prototype is tangible,
it allows stakeholders to experiment with a model
of the final product rather than being limited to
discussing abstract representations of their
requirements.
 Requirements documentation
As Output

Requirements documentation describes how individual

requirements meet the business need for the project.
Requirements may start out at a high level and become
progressively more detailed as more about the
requirements is known
 Requirements Traceability Matrix
As Output
The requirements traceability matrix is a grid
that links product requirements from their origin
to the deliverables that satisfy them. The
implementation of a requirements traceability
matrix helps ensure that each requirement adds
business value by linking it to the business and
project objectives.
 Project Scope Statement
As Output
The project scope statement is the description of the
project scope, major deliverables, assumptions, and
constraints.
The scope statement tells you what you have to do
 Product scope
 Deliverables
 Product acceptance criteria
 What is not part of the project
 Constraints and assumptions
 Create WBS
subdividing the major project deliverables and
project work into smaller, more manageable
components
• A WBS is a deliverable‐oriented grouping of the
work involved in a project that defines the total
scope of the project
• WBS is a foundation document that provides the
basis for planning and managing project
schedules, costs, resources, and changes
 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.
 Scope Baseline
As Outputs
• 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
• WBS dictionary : The WBS dictionary is a document
that provides detailed deliverable, activity, and scheduling
information about each component in the WBS
 Control Scope

Controlling changes to the project scope

Variance is the diff between planned and actual

performance
 Variance analysis
Variance analysis is a technique for determining
the cause and degree of difference between the
baseline and actual performance. Project
performance measurements are used to assess
the magnitude of variation from the original
scope baseline.
 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 chance of final product, service, or
result acceptance by validating each deliverable.
 Accepted Deliverables

Deliverables that meet the acceptance criteria are

formally signed off and approved by the
customer or sponsor.