Earned Value Calculation
Earned Value Calculation
ID Name
We would like to produce a weekly project update to the Chief Technology Officer. The earned
value method will give us metrics that include:
Schedule status
Budget status
End-of-project projections for both
For this project, because this is an example we will simply produce all of the earned value metrics in
one table.
Project Planning
As we showed you during the introduction, earned value analysis requires four things to be set up
during the project planning phase:
TOTAL $25,000
At this point we also need to make a few assumptions. Let’s assume it’s March 3 today and we are
doing the analysis up to the current point (today).
The Earned Value Calculation
To recap, the earned value calculation at each predefined status point is a 5 step process. Each
step has several variables that are calculated during that step
The Budget at Completion (BAC) simply refers to the budget of each task. Thus, we will rename the
budget column ‘BAC’:
TOTAL $25,000
Also called the Budgeted Cost of Work Scheduled (BCWS), the PV is the authorized, time-phased
budget assigned to accomplish the work. It is the amount that the project is supposed to be
complete up to that status point.
Let’s say it’s March 3 today. The planned percent complete is 30% based on the start and end
dates. Therefore,
Also called the Budget Cost of Work Performed (BCWP), the EV is the measure of the work
performed at a specific point in time, expressed in terms of the approved budget authorized for that
work. It is the amount that the project is actually complete up to that status point.
Let’s say that after discussions with the applicable project team members and inspection of the
progress, we determine that the first task is 20% complete and the second task is 10% complete.
Also called the Actual Cost of Work Performed (ACWP), the AC is the realized cost for the work
performed during a specific time period. It is the actual cost of the work up to that status point.
After reviewing our time and expense software and compiling any miscellaneous expenses, we
determine that the actual cost of the first task is $4,500 and the second task is $2,000.
This is the end of the information gathering phase. At this point the project manager transitions from
gathering project information to calculating project status.
In order to determine the project’s status as it relates to the schedule, we will calculate two variables
from the initial four we gathered from the project data, above:
The schedule variance tells you how far ahead or behind schedule the task is in terms of the task
budget. The formula is:
SV = EV – PV
Set up
100 Mar. 1 Mar. 10 $10,000 $3,000 $2,000 $4,500 -$1,000
Database
Build
200 Mar. 7 Mar. 20 $15,000 $0 $1,500 $2,000 $1,500
Application
As you can see, the project has a positive schedule variance because one task is ahead and the
other is behind.
The Schedule Performance Index (SPI) is similar to the Schedule Variance (SV). It also tells you
how far ahead or behind schedule the task is in terms of the task budget, but it is a relative measure
rather than an absolute one. It tells you the efficiency of the task. The formula is:
SPI = EV / PV
Build
20 Mar. Mar. $15,00 $1,50 $2,00
Applicatio $0 $1,500 N/A
0 7 20 0 0 0
n
It is easy to see that the first task has accomplished only two thirds of what it should have at this
point. Its efficiency is two thirds of that which was planned. But task 200 did not have any planned
value at this point, therefore its SPI is effectively infinity. It can simply be ignored in the rest of the
analysis.
In order to calculate the project’s status as it relates to the budget, we will calculated two more
variables:
The Cost Variance (CV) is the amount that the task is over or under its budget. The formula is:
CV = EV – AC
Build
20 Mar. Mar. 2 $15,00 $1,50 $2,00 N/
Applicatio $0 $1,500 -$500
0 7 0 0 0 0 A
n
The project is $3,000 over budget on a project value of $25,000. There is clearly a budget problem,
but not a schedule problem.
The Cost Performance Index (CPI), like the Cost Variance, is a measure of the cost performance of
the project, but it is a relative instead of an absolute measure. It tells you the cost efficiency of the
project. The formula is:
CPI = EV / AC
Build
20 Mar. Mar. $15,00 $1,50 $2,00 N/ 0.7
Applicatio $0 $1,500 -$,500
0 7 20 0 0 0 A 5
n
The first task has spent more than twice what it should have at this point because CPI < 0.5. The
second task is better but has spent one quarter too much. The project as a whole has spent just
under twice what it was budgeted to at this point (CPI = 0.54). Note that in the case of SPI and CPI,
the ‘total’ is an average, not a total.
This is the end of the metrics that tell you the current status. The last four variables give you
projections (forecasts) to the end of the project.
Forecasting
There are four variables which allow the project manager to forecast the future performance of the
project:
ETC represents the expected cost required to complete the project. It measures only
the future budget needed to complete the project, not the entire budget (that’s the EAC, next). It
allows the project manager to compare the funding needs to finish the project with funding available.
100 Set up Database Mar. 1 Mar. 10 $10,000 $3,000 $2,000 $4,500 -$1,000 0.67 -$2,500 0.44 $18,182
200 Build Application Mar. 7 Mar. 20 $15,000 $0 $1,500 $2,000 $1,500 N/A -$500 0.75 $18,000
TOTAL $25,000 $3,000 $3,500 $6,500 $500 0.67 -$3,000 0.54 $36,182
Many project managers wouldn’t concern themselves too much about this project yet. It has spent
$6,500 out of a project budget of $25,000. It’s still early, so there’s plenty of time to make up for it,
right?
Wrong. The ETC of $36,182 is the expenditure to complete the project assuming the prior efficiency
levels (a safe assumption). It also does not include the money already spent. If this project is not
brought under control soon, it will go wildly over budget and schedule.
Often there are unique circumstances which don’t allow for a simple extrapolation to the end of the
project. That’s where the Estimate at Completion (EAC) comes in.
You could also use a combination of the past schedule or cost performance to extrapolate the
final project cost. You could use only the schedule performance (SPI). Or you could figure in
a small influence of the schedule performance. In the formula below, 20% of the SPI and 80%
of the CPI has been used to determine the final project cost.
In our example we will predict that the current problems were caused by a one time event that isn’t
likely to repeat itself. Thus, the EAC will use formula #1.
Task 100: EAC = AC + (BAC – EV) = $4,500 + ($10,000 – $2,000) = $12,500.
Task 200: EAC = AC + (BAC – EV) = $2,000 + ($15,000 – $1,500) = $15,500.
100 Set up Database Mar. 1 Mar. 10 $10,000 $3,000 $2,000 $4,500 -$1,000 0.67 -$2,500 0.44 $18,182 $12,500
Build
200 Mar. 7 Mar. 20 $15,000 $0 $1,500 $2,000 $1,500 N/A -$500 0.75 $18,000 $15,500
Application
TOTAL $25,000 $3,000 $3,500 $6,500 $500 0.67 -$3,000 0.54 $36,182 $28,000
Now it looks alot better. The assumption of a one time cost expenditure near the beginning of the
project results in a final project budget of $28,000 versus the $25,000 original budget.
The VAC is a forecast of what the variance, specifically the Cost Variance (CV), will be upon the
completion of the project. It is the size of the expected cost overrun or underrun. In many situations
the project manager must request additional funding as early as possible, or at least report the
potential for an overrun. The VAC represents the size of this request.
This one is relatively simple. If you’ve calculated the EAC you’ve done the big math already, and the
‘new budget’ can simply be subtracted from the ‘old budget’ to determine the cost overrun or
underrun.
The Variance at Completion is simply a future projected Cost Variance. It has the same units as
CV. It is the same type of element.
Build
200 Mar. 7 Mar. 20 $15,000 $0 $1,500 $2,000 $1,500 N/A -$500 0.75 $18,000 $15,500 -$500
Application
TOTAL $25,000 $3,000 $3,500 $6,500 $500 0.67 -$3,000 0.54 $36,182 $28,000 -$3,000
Hence, the projected variance is -$3,000, and the project manager could obtain approval for the
expected overrun as early as possible, if necessary.
The TCPI represents the efficiency level, specifically the CPI, that will make the project finish on
time. It can be a powerful indicator because it is generally easy to ascertain if your people will be as
productive as the indicator tells you. This indicator tends to be a bigger red flag than other
indicators. If it says your people need to be twice as efficient as the schedule, it tends to make you
take notice that action needs to be taken.
Obviously, the closer the project is to completion the higher the CPI that will be necessary to
complete on budget. It can become extreme near the end.
Also, if the project has already spent more than its budget the TCPI will be negative.
TCPI is the last column in the table. We will assume the project budget has not been revised (EAC
is simply a projection) and the goal is still the original project budget (formula #1, above).
Task 100: TCPI = ($10,000 – $2,000) / ($10,000 – $4,500) = 1.45.
Task 200: TCPI = ($15,000 – $1,500) / ($15,000 – $2,000) = 1.04.
TOTAL: TCPI = ($25,000 – $3,500) / ($25,000 – $6,500) = 1.16.
ID Name Start End BAC PV EV AC SV SPI CV CPI ETC EAC VAC TCPI
Set up
100 Mar. 1 Mar. 10 $10,000 $3,000 $2,000 $4,500 -$1,000 0.67 -$2,500 0.44 $18,182 $12,500 -$2,500 1.45
Database
Build
200 Mar. 7 Mar. 20 $15,000 $0 $1,500 $2,000 $1,500 N/A -$500 0.75 $18,000 $15,500 -$500 1.04
Application
TOTAL $25,000 $3,000 $3,500 $6,500 $500 0.67 -$3,000 0.54 $36,182 $28,000 -$3,000 1.16
This project team must be 16% more efficient than they have been to finish on budget.
This table can be reported directly to management. They might need some training on what the
numbers mean but this is not an onerous task.