Skip to main content

Validating The Project Estimate

A project manager should be familiar with the procedural and/or legal requirements associated with the use of project contingency. In many situations the owner thinks of the contingency as the amount of funding available to add more scope if need be. The project manager typically views the contingency, as funds to be tapped, if the project is delayed for whatever reason. Contingency should cover the uncertainty for risks that are difficult to estimate portions of the project. Therefore, it's important that the documentation surrounding the use of the contingency amounts is well documented. It will come in handy when meeting with the client on project changes.

When validating project estimates, check:

- Level of Detail In The Requirement Document

- The Method Of Estimating Utilized
- The Experience Of The Estimator

In any case, it is safe always to estimate a contingency value, that is the amount of “set a side” in dollars or hours, which is over and above the initial project estimate. This is necessary to cover risk related items and to provide coverage for items that were difficult to identify in detail during the time the estimate was prepared. Risk and contingency are interrelated, the higher the risk the greater need for contingencies.

Contingency estimating is a tricky process, and it's best to follow a process

-Verify mitigation approach or steps to the solution
-Consider the degree of uncertainty (subjective) associated with each
-Add a percentage amount 10, 20 % etc. The percentage amount is based on:
-Contract Provision

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…