Skip to main content

Project Cost Estimate vs. Cash Flow Analysis

A follow up based on my previous post: analyzing graph of planned project cost against cash flow. 

A simple comparison can be done using the WBS (Work Breakdown Structure) elements that contain all the tasks (the work to be done) of the project not yet realized. Each task has a cost assumption. Since WBS have a child / parent relationship, it's possible to roll up and summarize the cost information from the lower levels and upwards. The summarized total cost is the project cost estimate (or budget).

As the project advances, it's possible to validate the project cost estimate against the cash flow (actual cost). A good estimate makes a better forecast of project cost at completion (close to the final actual cost).

Project Cost Estimate and Cash Flow Analysis
**The above graph illustrates three curves and is based on a hypothetical project with a number of tasks with an equal amount of work distributed equally over time,

  1. The green curve is the ideal case. In an ideal situation the beginning is usually slow because the project team normally acquires confidence with the project. Once the schedule has achieved 20-30% of the work, the slope of the graph will change and will accelerate due to the confidence and knowledge acquired. At 70-80% the schedule has reached a very good level of control and will continue with confidence to full completion of the project.
  2. The red curve is a representation of an early schedule spending too much money at an early stage. In this case, there is a risk to go over the budget, make mistakes, hence, not completing the project has planned.
  3. The blue curve is a representation of a late schedule. In this case, there is a  risk to work in a hurry toward the end, without the possibility of correcting possible mistakes.
**Graph to be re-defined.

In order to compare the project cost estimate with the cash flow at any given point in the timeline of the project, there is a need to know the actual cost of the work done. This data can be obtained from the organization 's accounting system or from the team that keeps track of the financial aspect of the project. 

To analyze, and not only compare, in order to get more meaningful information of the project cost estimate against the cash flow at any given point, it's necessary to verify how much work has actually been completed to that point. This can be achieved with the Earned Value method. Please see my previous two posts for this topic:

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…