Project Scope

Management

Why Do We Manage Scope?

Cant manage schedule
(time) and budget (cost)
if scope is out of control
(Triple Constraint)
Scope is about
SCOPE
managing stakeholders
expectations for the
benefit of the project
success.

TIME

Quality
COST

What is Project Scope Management?

The processes required to ensure that the project includes all
the work required, and only the work required, to complete
the project successfully

Processes

Each of
these
processes
have ITTO

One of the key elements in managing scope is to prevent

scope creep (any uncontrolled change to a Project)

Plan Scope Management

A process that defines how scope will be defined, validated, and
controlled.

Plan Scope Management

Scope management plan defines the activities needed to determine and
manage the project scope. It uses the project charter, the preliminary project
scope statement and the project management plan to develop the scope
management plan.
It assists in lessening possible future issues of scope creep, project changes,
conflict issues and project risks. It is a subsidiary component of the project
management plan.
It includes:
How the scope will be defined, developed, monitored, controlled, and verified
How minimize or eliminate scope creep
How to deal with disagreements from stakeholders on scope
Process for preparing a detailed scope statement
Process for the creation and the maintenance of the WBS
Process that defines how acceptance criteria
Process that defines how requested changes will be processed

Plan Scope Management

Requirement management plan:
Defines how requirements will be identified, planned, tracked,
and reported
Process for addressing missed requirements.
Process for the prioritization of requirements.
Metrics that will be used to trace the requirements

Collect Requirements

Requirement : A condition or capability that must be met by a product or

service to satisfy stakeholders expectations
Requirements include the quantified and documented needs, wants, and
expectations of stakeholders.
In short, what the customer needs from the project in order for the project to
be successful.

Collect Requirements

Requirements Collection Tools

COLLECT REQUIREMENTS
Requirements documentation (Output)
Justifies why each requirement is important. Information captured
here should include:

Source of the requirement and problem that is being solved

How each requirement addresses the problem
Relevant measurements for each requirement
Constraints and assumptions
Predicted impact of the requirements on others
Potential legal, and ethical compliance related to
requirements

COLLECT REQUIREMENTS
Requirement Traceability Matrix (Output)
A traceability matrix is a used to track the requirements and to
check whether the current project requirements are met.
Requirement Traceability Matrix captures all requirements
proposed by the client or development team and their
traceability in a single document delivered at the conclusion of
the life-cycle.
In other words, it is a document that maps and traces user
requirement with test cases. The main purpose of Requirement
Traceability Matrix is to see that all test cases are covered so
that no functionality should miss while testing.

COLLECT REQUIREMENTS
Advantage of Requirement Traceability
Matrix
It confirms 100% test coverage
It highlights any requirements missing or document
inconsistencies
It shows the overall defects or execution status
with a focus on business requirements
It helps in analyzing or estimating the impact on reworking test cases

Requirement Traceability Matrix

PROJECT SCOPE MANAGEMENT

DEFINE SCOPE
DEFINE SCOPE
Describes the boundaries of the project and product by
defining which of the requirements collected will be included
in and excluded from the project scope.
A preliminary scope statement was prepared in the develop
project charter process, and now it is refined here with
additional information about the project.
Key output of the scope definition process (define scope)

PROJECT SCOPE MANAGEMENT

DEFINE SCOPE

Define Scope
Scope Statement (key output of the scope
definition process) is the basis for project
decisions and is critical to project
success.
It details what is included in the project,
what is not included in the project.
It contains enough information to allow
stakeholder their agreement on the:

Projects justification
Projects product
Projects exclusions
Projects deliverables
Projects constraints and assumptions
Projects acceptance criteria

PROJECT SCOPE MANAGEMENT

DEFINE SCOPE
Photo Mobile Application
(Requirements)

IN SCOPE

OUT OF SCOPE

PROJECT SCOPE MANAGEMENT

DEFINE SCOPE

Create WBS

Scope baseline is the approved project scope

statement along with the WBS and WBS dictionary.

Work Breakdown Structure

New Warehouse

Design - 1

Construction - 2
Structural - 1.1

Commissioning - 3
Concrete Install 2.1

Steel Package 1.1.1

Steel Install 2.2

Concrete Package 1.1.2

Drywall Install 2.3

1st Floor Package 2.3.1

Architectural 1.2
Floor Layout 1.2.1
Elevations 1.2.2
Door Schedule 1.2.3

2nd Floor Package 2.3.2

Create WBS
WBS
A process for breaking down a project deliverable into smaller, more
manageable parts (structured hierarchy).
WBS It defines the total scope of the project using descending levels
o detail concerning the work that must be done.
It provides input to other planning processes such a scope control,
activity definition, cost estimating, cost budgeting and plan
purchases and acquisitions.
Responsibility Assignment Matrix is a tool that links the WBS
components to the roles, responsabilities and resources required to
achieve each element of WBS.
Work package is the lowest-level item of the WBS. Cost estimates
are made at this level. Schedule activity is a further division of the
work package.

Create WBS
WBS Dictionary
It provides specific details about the elements of the WBS
defining ownership, responsabilities, due dates, dependencies
and acceptance criteria, among other element.
Notice that in addition to the fundamental information (name,
owner, resources, due date, cost, duration, acceptance
criteria, etc.) also provides informations abourt dependencies
onf the prior activity or the following activity. Development of
the WBS dictionary often allows identifying ambiguity or other
erros in the WBS itself, and results in revisions to the WBS

Create WBS
Benefits of Using WBS
Effort to produce the deliverable can be confidently estimated
Types of skills required to produce the deliverable can be
identified and evaluated
Required resources can be determined
Costs can be confidently estimated
Deliverables can be easily tracked.
Brings focus to project objectives
Facilitates status reporting
Facilitates problem analysis, tracking of time, cost and
performance
Clearly defines responsibilities
Available for reuse for similar projects.

Verify Scope

Scope validation primarily concerns itself with formal acceptance of

deliverables by the customer. It can occur not only at the end of
the project, but also at the end of every project phase. Delivered
scope elements can be verified progressively as the project unfolds.

Validate Scope vs Control Quality

Control Scope

Controlling scope means that you are measuring the work

product against the scope baseline and that you are doing so
frequently to ensure that the project stays on track.

Control Scope
Controlling Scope means that:
You have verified the scope against the requirements
traceability matrix
You are measuring project performance against the scope
baseline using variance analysis techniques to determine
whether preventive or corrective actions are required
You are determining the impact of scope changes against
the timeline, budget, quality and product configuration

Control Scope
Preventing or eliminating scope creep on a
project demands the implementation of an
enforced change control system that requires:
All requested scope changes must be documented
All requested scope changes must perform an impact
assessment
All requested scope changes must be reviewed by the
customer, the performing organization and the CCB (change
control board)
All requested scope changes can be either accepted or rejected