Welcome To PMCDP 2003 PMP Training at Mumbai Day - 2
Welcome To PMCDP 2003 PMP Training at Mumbai Day - 2
■ Initiation
■ Scope planning
■ Scope definition
■ Scope Verification
Tools and
Inputs Outputs
techniques
Project selection
Product description Project charter
methods
PM
Strategic plan Expert judgement
identified/assigned
Project selection
Constraints
criteria
Historical information Assumptions
Scope Planning
Scope planning is the process of progressively elaborating and
documenting the project work that produces the product of the project
Tools and
Inputs Outputs
techniques
Scope statement WBS templates WBS
scope statement
Constraints Decomposition
updates
Assumptions
Other planning outputs
Historical information
WBS -Decomposition
■ Identify the major deliverable
■ OBS/RBS – difference
Related reference : Project Management a systems approach to planning, scheduling and controlling – Dr Herold Kerzner – Pages 535 - 554
Scope Verification
Scope verification is the process of obtaining formal
acceptance of project scope by the stakeholders
Key processes:
– Activity definition
– Activity sequencing
– Activity duration estimating
– Schedule development
– Schedule control
Activity Definition
Identifying and documenting the specific activities that must be performed
in-order to produce the deliverables and sub-deliverables identified in
WBS
■ Finish Start (FS): the from activity must finish before the
to activity can start (Testing to verification)
■ Start Start(SS): The from activity must start before the to
activity can start( coding and code reviews)
■ Finish-Finish: The from activity must finish before the to
activity can finish (Completion of coding and functional unit
testing)
■ Start-Finish: The from activity must start before the to
activity can finish(Product launch Vs Product GA/LA)
Activity Sequencing Techniques
B
A
Arrow C
Diagramming Start
Method D Finish
F
E
Precedence A B
Diagramming
Method
Start Finish
Arrow Diagramming Method (ADM/AOA)
C B
Activity Duration Estimating
…..involves assessing the number of work periods likely needed to complete each identified
activity
Identified Risks
Schedule Development
……. involves determining start and finish date of project activities
Inputs Tools and techniques Outputs
Project network
Mathematical analysis Project schedule
diagram
Activity duration
Duration compression Supporting detail
estimates
Resource
Simulation Schedule mgt plan
requirements
Resource pool Resource leveling Resource requirement
description heuristics updates
Project management
Calenders
software
Contraints Coding structure
Assumptions
Leads and Lags
Risk Mgt Plan
Activity Attributes
Tools and Techniques for Schedule
development
■ Mathematical Analysis
– Critical Path Method
– Program Evaluation and Review Technique
– Graphical Evaluation and Review Technique
■ Duration Compression
– Crashing
– Fast tracking
Schedule control
■ Event
■ Activity
testing
Start testing Complete testing
PERT and CPM
Both PERT and CPM uses dummy activity to develop the logic
Sample Network
3
2 6
6
2
7
1 7
3
5
3 5
5
TE = 2 TE = 5
3
2 6
6
2
TE = 0 7 TE = 14
1 7
3
5
3 5
5
TE = 9
TE = 3
TL = 2 TL = 8
3
2 6
6
2
7 TE = 14
TL = 0 1 7
TL = 14
3
5
3 5
5
TL = 9
TL = 4
TE = 2 TE = 5
TL = 2 TL = 8
3
2 6
6
2
TE = 0 7 TE = 14
1 7
TL = 0 TL = 14
3
5
3 5
5
TE = 9
TE = 3
TL = 4 TL = 9
■ Expected time
Te = (a+4b+c)/6
PERT – Estimated activity time
2, 3, 4 4, 7, 10 3, 5, 7
A B C D
Te = 3 Te = 5
Te = 7
■ Resource planning
■ Cost estimating
■ Cost control
Resource Planning
Project Management
Scope statement
Software
Organisation Policies
C ost B udgeting
Inputs Tools and techniquesOutputs
C ost estimates Analogous estimating C ost Baseline
W BS Parametric modelling
Project schedule Bottom up estimating
C omputerised tools
Cost Control
Cost control
Inputs Tools and techniques Outputs
Cost change control
Cost baseline Revised cost estimates
system
Performance
Performance reports Budget updates
measurement
Earned Value
Change requests Corrective action
Management
Cost management plan Additional planning Estimate at completion
Computerised tools Project Closeout
Lessons learned
Basic Earned Value Management
for
Project/Program Managers
Why use EVMS?
■ Status:
– spent to date: $64,000
– time elapsed: 6 months
– units produced: 8 complete, 2 partial
■ How are you doing, and how do you know how you are doing?
to measure progress
What do we measure progress
against?
time
Five Basic Elements
It’s my pleasure
to award you
this contract for hmm...5 miles of
a new railroad track, 5 months to do
it all....$5000
track
budget....This
is going to be tough!
Budgeted Cost of Work Scheduled
(BCWS)
Month 4 Month 5
BCWS = $1,000 BCWS = $1,000
each
eachdollar
dollarof
ofBCWS
BCWSrepresents
representsaaspecific
specificdollar
dollarof
ofwork
workscope
scope
Budgeted Cost of Work Scheduled
(BCWS)
Month 4 Month 5
BCWS = $1,000 BCWS = $1,000
BCWS
BCWSis isaggregated
aggregatedand
andsummed
summedas
asthe
the
performance
performancemeasurement
measurementbaseline
baseline
Budgeted Cost of Work Performed
(BCWP)
You
Youearn
earnvalue
valuethe
thesame
sameway
way
as
asititwas
wasbudgeted
budgetedin inbaseline
baseline
Schedule Variance
SCHEDULE
SCHEDULEVARIANCE
VARIANCEisisthe
thedifference
differencebetween
betweenwork
workscheduled
scheduled
and
andwork
workperformed
performed(expressed
(expressedininterms
termsofofbudget
budgetdollars)
dollars)
formula:
formula: SV
SV$$==BCWP
BCWP--BCWS
BCWS
example:
example: SV
SV==BCWP
BCWP--BCWS
BCWS==$1,000
$1,000--$2,000
$2,000
SV= -$1,000
SV= -$1,000 (negative
(negative==behind
behindschedule)
schedule)
Schedule Variance
5,000
BCWS
“the baseline”
sv
$
BCWP
“earned value”
TIME 5 months
Budget at Completion (BAC)
= BAC
CWS $5,000
$5,000
ll B
$ o fa
m
su
$
$
$ $
$
$
$
time
•• when
whenall
allwork
workhas
hasbeen
beenphased,
phased,cumulative
cumulativeBCWS
BCWS==BAC
BAC
e.g.,
e.g., $5,000
$5,000==$5,000
$5,000
At the end...
■ At the end of the contract, when all work has been completed:
– I’ve “earned” all of my budget ($5,000)
• BCWP (cumulative) = $5,000
• BCWS (cumulative) = $5,000
■ Example:
actual
actualexpenditures
expendituresvs.
vs.budget
budget
Cost Variance
PERFORMANCE
BCWP of the work I actually performed,
how much did I budget for it to cost?
BASED
of the work I actually performed,
BCWP how much did it actually cost?
COST
COSTVARIANCE
VARIANCEisisthe
thedifference
differencebetween
betweenbudgeted
budgetedcost
cost
and
andactual
actualcost
cost
formula:
formula: CV
CV$$==BCWP
BCWP--ACWP
ACWP
example:
example: CV
CV==BCWP
BCWP--ACWP
ACWP==$1,000
$1,000--$2,400
$2,400
CV= -$1,400
CV= -$1,400 (negative
(negative==cost
costoverrun)
overrun)
Cost Variance
5,000
ACWP
“actual cost”
cv
$ BCWP
“earned value”
TIME 5 months
Estimate at Completion
(EAC)
VARIANCE
VARIANCEAT
ATCOMPLETION
COMPLETIONisisthe
thedifference
differencebetween
betweenwhat
whatthe
thetotal
total
job
jobisissupposed
supposedto
tocost
costand
andwhat
whatthe
thetotal
totaljob
jobisisnow
nowexpected
expectedto
tocost.
cost.
FORMULA:
FORMULA: VAC
VAC==BAC
BAC--EAC
EAC
Example:
Example: VAC
VAC==$5,000
$5,000--$7,500
$7,500
VAC
VAC==--$2,500
$2,500 (negative
(negative==overrun)
overrun)
Variance at Completion (VAC)
= BAC - EAC
EAC
VAC
BAC
TIME
FIVE BASIC PERFORMANCE DATA
QUESTIONS & ANSWERS
5,000
BCWS
ACWP
cv
$ sv
BCWP
TIME 5 months
COST
COSTPERF
PERFINDEX
INDEX(CPI)
(CPI)== BCWP
BCWP
ACWP
ACWP
1.2
SCHED
SCHEDPERF
PERFINDEX
INDEX(SPI)
(SPI)== BCWP
“GOOD”
BCWP
BCWS
BCWS
1.1
TIME
1.0
CPI
.9
“BAD”
SPI
.8
Schedule Status
TIME NOW
BCWS
% scheduled = BCWS x 100%
BAC
compare BCWP
budget
budget status
status
%
%spent
spent == ACWP
ACWP xx 100%
100%
BAC
BAC
compare:
compare:
%
% spent
spent vs.
vs. %
% complete
complete
example:
example: 60%
60%spent
spentvs.
vs.50%
50%complete
complete
What will be the final cost?
EAC = BAC
CPI
.8(CPI) +.2(SPI)
CPI * SPI
Other methods of EAC calculation
– Positive VAC:
• EAC < BAC underrun contractor gain
– Negative VAC:
• EAC > BAC share area contractor partial loss
• EAC > ceiling overrun contractor loss (100%)
■ Gary Christle, 22 Jan 94, paper, Implementation of Earned Value - A Model Program
Approach
■ USD(A&T) Letter, 25 Jan 94, Improved Cost and Schedule Performance Management
■ Gary Christle, 15 Sep 94, paper, The Cost/Schedule Control Systems Criteria and Earned
Value Management: A Vision
■ USD(A&T) Letter, 1 Oct 96, Compliance Responsibility for the Cost/Schedule Control
Systems Criteria (C/SCSC)
■ 3 Oct 97, Earned Value Management Implementation Guide (Rev 1)
■ USD(A&T) Letter, 14 Dec 96, Industry Standard “Guidelines for Earned Value
Management Systems”
■ Wayne Abba, article in Jan-Feb 97 Program Manager magazine, Earned Value
Management - Reconciling Government and Commercial Practices
■ ANSI/EIA 748-1998, Earned Value Management Systems
■ Quentin W. Fleming & Joel M. Koppelman, book, Earned Value Project Management