Project Monitoring and Controling
Project Monitoring and Controling
1
Project Management Process
Groups
Project Monitoring and Control
Monitoring – collecting, recording, and
reporting information concerning project
performance that project manger and others
wish to know
Controlling – uses data from monitor activity
to bring actual performance to planned
performance
Outputs include performance reports,
requested changes, and updates to various
plans
Chapter 9 Project Monitoring & Control 3
Why do we monitor?
Simply because we know that things
don’t always go according to plan (no
matter how much we prepare)
To detect and react appropriately to
deviations and changes to plans
6
Progress Monitoring
The 3 key Progress Monitoring
Questions
What is the actual status?
If there’s a variance, what is cause?
What to do about it?
Possible responses
1. Ignore
2. Take corrective action
3. Review the plan
7
Progress Monitoring
Monitoring rates
Daily, weekly, monthly
If problems occur – then adjust
You may have to monitor problem areas more closely
For some period of time
Almost always there’s one or more areas under closer
scrutiny
Status Reporting
Part of the communications management plan
8
Status Reports
From team to PM, from PM to stakeholders
Typical format for letter
Summary
Accomplishments for this period (done)
Tasks, milestones,
Plans for next period (to-do)
Risk analysis and review
Issues & Actions
Shoot for weekly updates
Email notes, then hold brief meeting
More frequently during crises
9
Traffic Light Assessment
Identify the key element
Break these key element in constitute element
Access each second level element
Green (on target)
Amber (not on target but recoverable)
Red (not on target but recoverable with difficulties)
Review all the second level assessment to arrive at
first level assessment
PLAN
Specifications
ACTION Project Schedule
Correct Project budget
deviations Resource plan
MONITOR
from plan Vendor contracts
Record status
RE-PLAN as Report progress
Report cost
necessary
COMPARE
Actual status
against plan
-Schedule
-Cost
16
Derived EVA Variances
SV: Schedule Variance
BCWP – BCWS
Planned work vs. work completed
CV: Cost Variance
BCWP – ACWP
Budgeted costs vs. actual costs
Negatives are termed ‘unfavorable’
“What is the project status”?
You can use variances to answer this
17
Derived EVA Ratios
SPI: Schedule Performance Index
BCWP / BCWS
CPI: Cost Performance Index
BCWP / ACWP
Interpretation of Indexes
18
Earned Value Analysis
Other Derived Values
BAC: Budget At Completion
Sum of all budges (BCWS). Your original budget.
Planned Value (PV) at the end of the project
EAC: Estimate At Completion
Forecast total cost at completion
EAC = ((BAC – BCWP)/CPI) + ACWP
Unfinished work divided by CPI added to sunk cost
If CPI < 1, EAC will be > BAC
CR: Critical Ratio
SPI x CPI
1: everything on track
> .9 and < 1.2 ok
Can be charted
19
EVA Example-1
You have a project to be completed in 12 months and total cost of
project is $100,000. Six months have been passed (and schedule says
that 50% of work should be completed).
Six months have been passed and $60,000 is spent but on closer look
you find that only 40% of work is completed so far.
Planned Value (BCWS)
Project duration – 12 months
Project Cost (BAC) = $100,000
Percent complete – 50% (as per the schedule)
Planned Value = 50% of value of total work
= 50% of BAC
= 50% of $100,000
= (50/100)X $100,000
= $50,000
22