PM Life cycles-Scope

assessment & WBS creation

 Customer acceptance

PM LIFE CYCLE and deliverables report

Deliverables from
each phase
Status reports
Issue logs
Change logs
Project charter Project charter
Metrics
Inputs Business case Lessons learned Approved
Corrective actions
Project Plan

Execution and
Process Initiating Planning Closure
control

Deliverables from Transferred

Outputs Approved Approved
each phase artifacts to the
Project charter Project Plan
Status reports repository
encompassing
Issue logs Lessons learned
all knowledge
Change logs Release of
areas
Metrics resources
New risks (if any)
Decisions on Project
continuation
Corrective actions
 Interaction Between Engg and Project mgt
Status, changes
Customer acceptance
issues,results,evaluations,measures
report Project execution and analysis
Deliverables from each
and control
phase Corrective actions
Status reports
Issue logs
Change logs
Replan What to monitor
Metrics
Commitments
New risks (if any)
Corrective actions Engineering
Project Planning What to build
Processes
What to do

Project charter
Project Closure

Project Initiation
Business case
DEFINITION OF SCOPE MANAGEMENT PROCESSES

SCOPE MANAGEMENT INCLUDES PROCESSES

REQUIRED TO ENSURE THAT THE PROJECT SCOPE
INCLUDES ALL THE WORK REQUIRED TO MEET
PROJECT OBJECTIVES, AND ONLY THAT WORK
WHICH IS REQUIRED TO COMPLETE THE PROJECT.
 PROJECT SCOPE

Project scope
is the work that must be performed to
deliver a product, service or result with
specified features, functions and satisfaction
criteria.
Location
No of levels in the hierarchy
Target audience
 Scope Management

The major focus of the Scope Management Knowledge Area

is the Elicitation/analysis and specifying of client
requirements.

This linkage begins with the project description document

and extends to the project plan and its execution, including
monitoring progress against the project plan and the
integration of changes, and finally through to project
closure.
Scope Management Client Wants vs. Client Needs

NEEDS

WANTS

What your client wants may not

be what your client needs.
Scope Management
Following requirements gathering and documentation,
you choose the best-fit project management life cycle
and develop the Work Breakdown Structure (WBS) that
defines the work to be done to deliver those
requirements.

That prepares the team and the client with the

information they need to estimate time, cost, and
resource requirements.

The Scope Management Knowledge Area overlaps the

Scoping and the Planning Process Groups.
PROJECT SCOPE MANAGEMENT PROCESSES

PLANNING GROUP:

COLLECT REQUIREMENTS

DEFINE SCOPE

CREATE WBS

MONITORING & CONTROLLING GROUP:

VERIFY SCOPE

CONTROL SCOPE
Project Scope Management Process flow

Collect
Define Scope Create WBS
Requirements

Yes

No Any
Control Scope changes Verify Scope
?
 COLLECT REQUIREMENTS

COLLECT REQUIREMENTS IS THE PROCESS OF DEFINING AND

DOCUMENTING THE NEEDS TO MEET THE PROJECT OBJECTIVES
DEFINE SCOPE
DEFINE SCOPE IS THE PROCESS OF DEVELOPING A
DETAILED DESCRIPTION OF THE PROJECT AND THE
PRODUCT OF THE PROJECT.THE OUTPUT OF THIS
PROCESS IS PROJECT SCOPE STATEMENT
 CREATE WBS

Create WBS is the process of subdividing the project

deliverables into smaller and more manageable
components.
WBS is defined as a deliverable oriented hierarchical
decomposition of the work to be executed by the project
team to accomplish the project objectives and create
deliverables.
It organizes and defines the total scope of the project.
Each descending level represents an increasingly
detailed definition of the project work. The WBS is
decomposed into work packages
 VERIFY SCOPE

PROCESS OF FORMALIZING THE ACCEPTANCE OF

COMPLETED PROJECT DELIVERABLES
CONTROL SCOPE

THE PROCESS OF MONITORING THE STATUS

OF THE PROJECT AND PRODUCT SCOPE AND
MANAGING CHANGES TO SCOPE BASELINE
KEY ISSUES IN PROJECT SCOPE MANAGEMENT

No sign off for the requirements

Inability to prioritize the requirements with appropriate stakeholders
Indiscriminate and uncontrolled scope creep
Inexperienced people involved in requirements gathering and scoping .
Eliminating ambiguity
No processes to define and manage scope