Skip to main content

Multiple Projects Performance Analysis using the Earned Value Method

The assumption made here is that anyone reading this example has some background in Earned Value Management. If not please consult this link Earned Value Management for related literature and references.

For the purpose of illustrating this method, I have created a table containing three hypothetical projects with their respective baselines. Each baseline is defined in terms of duration, effort and cost for each single project.

The idea is to carry out a performance control half way down the timeline for each project and verify that all projects are in line with their respective plan. This could be a major milestone or a check point. Normally, there are many planned check points throughout the life cycle of a project, but for the purpose of this example only one point is taken into consideration.

This method uses the actual cost of the work done, at a given point, and the planned cost to calculate and compare values for cost and schedule variations. This information is also calculated in terms of cost and schedule performance indexes.

The actual cost factor is what really links the operating company to the ongoing project and could comprimise the project or the company or both if not properly monitored and controlled.

The following table summarizes the calculations needed for graphing and deducing the results relative to project performance at a given point.

Cost and Schedule Variances

Variances: positive variance is good; negative is bad.

Situation at half time:
Project A: CV is less than 0 and SV is greater than 0; the cost of the actual work exceeded the value of the work done (the project is over budget and ahead of schedule).
Project B: CV is less than 0 and SV is less than 0; the amount of work done is inferior to the budgeted amount.
Project C: CV is greated than 0 and SV is greater than 0; the cost of the actual work is inferior to the value of the work done and the amount of work produced exceeded the budgeted amount.

Atlhough Project A is ahead of schedule, it's using up too much money too fast with respect to the plan. The risk is that it will use up all the budget before completion of the project.

Cost and Schedule Performance Index

Performance index: greater than 1 is good, less than 1 is bad.

Popular posts from this blog

The differences between Project, Operation and Program

We said that a project is defined as a temporary endeavor that consumes resources, incurs cost and produce deliverables over a finite period of time to achieve a specific goal. They come in all shapes and sizes and can vary in length or complexity.

Operation type activities are similar to project activities in that they too produce deliverables, consume resources and incur cost. However they are on-going or repetitive in nature, hence they are not project activities or tasks. Some examples of operation activities are weekly maintenance of databases, paying invoices or help desk operations activities.

Programs are much larger than projects. They are made up of many projects and on going activities such as operation type activities and are similar to projects as they consume resources, incur cost and produce deliverables. However programs are more complex and include repetitive operation type activities such as maintenance work, facility administration etc, and are funded typically on a…

Forecasting Project Costs using Variance Analysis

One way to report on cost control and forecasting during project execution is to use the Variance Analysis method, that is, explaining the difference (or variance) between actual costs and the budgeted costs with numbers and make new estimates for completing the work. Please consult this link Earned Value Management for related literature and references.
For the purpose of making these calculations, I will use an hypothetical project example (but it could also be a task or phase). "A company has contracted a service provider to deliver a project in 10 working days (80 hours) for the estimated cost of $10,000 and a work effort of 200 hours. The contract is Time and Material, this means that the company pays the provider for the number of hours actually required to perform the service. So, the provider has no incentive to minimize the number of hours expended on the service. The less efficient the provider is, the more money it makes!"
Summary of Time and Material Contract (re…

Using PERT for estimating tasks

A simple way for estimating tasks is to use the PERT (Program Evaluation review technique) weighted average method. This method uses a weighted average duration estimate to calculate task duration, it gives the opportunity to take into account information based on different types of estimates values (such as poorly defined areas, probabilistics, and ranges for the schedule). This method is based on the Beta distribution model because it can model events which are constrained to take place within an interval defined by a minimum and maximum value. (For this reason, the Beta distribution is used extensively in PERT, CPM and other project planning/control systems to describe the time to completion of a task).

The term weighted average means that the equation uses weighted factors to calculate the expected task duration.
The equation and process modelling a task for PERT is the following:  E=(O+4M+P)/6 (equation)  E= Expected Value  O= Optimistic Value (this is equivalent to a minimum val…