it’s amazing how many projects do not know their true status until near the end, when there is little that can be done to ensure they finish on time or budget.

the proper time to rigorously track project status is at the beginning, * not* at the end. this is when project risk can be managed and changes made to get it back on track.

earned value analysis is the current buzzword for effective project control. it focuses on the two main variables that are inevitably crucial for every project.

- schedule (time)
- cost

there are 7 steps to performing earned value analysis effectively. it may seem like alot at first glance, but for small projects this takes five minutes once you learn how to do it:

- determine the percent complete of each task.
- determine planned value (pv).
- determine earned value (ev).
- obtain actual cost (ac).
- calculate schedule variance (sv).
- calculate cost variance (cv).
- compile the results.

before you get started, it is important to define appropriate project status points in which this calculation is performed. weekly status meetings work very well, but whatever system you use make sure it is adhered to rigorously.

## determine percent complete

to start the process, the percentage complete of each task needs to be determined. some project managers feel that each task should be sized so that the task can only be 0, 50, or 100% complete (not started, in progress, or complete). this prevents abuse when project team members exaggerate, for example they might tell you a task is 80% complete when it is really 50% complete. for repetitive tasks you can also use progressive measures such as number of fence posts installed. whichever method you use, this is the primary input into the process and each task needs to be defined with a percent complete.

## determine planned value (pv)

** planned value**, also known as

*, is defined as the amount of the task that is supposed to have been completed. it is in monetary terms as a portion of the task budget. for example,*

**budgeted cost of work scheduled (bcws)**- the task budget is $5,000,
- the task start date is january 1, and
- the task finish date is january 10.

if it’s january 6 today, the task is supposed to be 60% complete. *pv = $5,000 x 60% = $3,000*.

## determine earned value (ev)

* earned value*, also known as

*, is the amount of the task that is actually complete. it is, again, in monetary terms as a portion of the task budget. for example,*

**budgeted cost of work performed (bcwp)**- the task budget is $5,000, (same as above)
- the task start date is january 1, and (same as above)
- the task finish date is january 10. (same as above)

let’s say the actual percent complete of the task (step 1) is 40%. *ev = $5,000 x 40% = $2,000*.

## obtain actual cost (ac)

the * actual cost*, also known as

*, as you might guess, is the actual cost of the work. generally employee hours need to be converted into a cost, and all project costs need to be added up, such as the following items:*

**actual cost of work performed (acwp)**- labor
- materials
- equipment
- fixed cost items, like subcontractors

since most projects have these well defined via accounting or project management software, i will not go into great detail here. for the purposes of the next section, let’s say the actual cost of the example task is $1,500.

## calculate schedule variance (sv)

the schedule variance represents the schedule status of the project.

in our above example the schedule variance is: *sv = $2,000 – $3,000 = -$1,000*.

a negative schedule variance means the task is behind schedule. a positive schedule variance means it is ahead of schedule. the amount can be compared to worker charge out rates or similar metrics to get an idea of how difficult it would be to recover.

## calculate cost variance (cv)

the cost variance represents the cost status of the project.

in our above example the cost variance is: *cv = $2,000 – $1,500 = $500*.

a negative cost variance means the task is over budget. a positive cost variance means it is under budget.

## compile the results

once the individual task sv’s and cv’s have been calculated, they need to be added up into overall project variances. this represents the total variance of the project and can be reported to management, clients, and stakeholders.

## other status indicators

although the sv and cv are the minimum requirement and work well for small projects, there are other variables that are derived from them which you might want to calculate:

**schedule performance index (spi):**the schedule variance expressed in percentage terms, for example, spi = 0.8 means the project 20% behind schedule.spi = ev / pv**cost performance index (cpi):**the cost variance expressed in percentage terms, for example, cpi = 0.9 means the project is 10% over budget.cpi = ev / ac**estimate at completion (eac):**the expected budget at the end of the project given the variances that have already taken place.eac = ac + bac – ev**estimate to complete (etc):**the expected cost to finish the rest of the project.etc = eac – ac**to complete performance index (tcpi):**the required cpi necessary to finish the project right on budget. for example, tcpi = 1.25 means you need to find 25% efficiencies to finish on budget.tcpi = (bac – ev) / (bac – ac)

## interpreting the results

if the schedule variance is negative, you are behind schedule. if the cost variance is negative, you are over budget. the actual amount of variance can be compared to employee charge out rates or something similar to ascertain how difficult it might be to recover. the results are as instantaneous as the input data, that is if you input the percent complete as of right now, the status reported will be as of right now as well.

in our example the schedule variance was -$1,000 and the cost variance was $500. this means that the project is being schedule, but it is being performed efficiently and is cost-positive. if an auditor charging $75/hr was performing the majority of this work, they are about 13 hours behind schedule. this requires a couple days of work over and above the regular schedule to get back on track.

graphing the results over multiple status points is a very helpful exercise. good project control often means that the instantaneous project status snapshot is not as important as the trend the indicators are making over time. for example, if the sv has been increasing, then maybe the project will finish on time even though it’s behind schedule today.

it is a well understood concept that if projects fall behind early they will tend to struggle throughout their entire life cycle, and earned value analysis will give you that picture.

## leave a reply