Skip to main content

Project behaviour during lifecycle

What is the behaviour of the curve during different time intervals, such as at (0), (0, 20-30%], (20-30%, 50%], (50%, 75%], and (75%, 100].

Brief analysis and points of discussion

Since a project has a temporary endeavor, the timeframe has to be finite. The broken lines in the graph represent finite areas such as phases or milestones. The black graph represents the estimated project plan schedule, the blue graph represents an early schedule, and the red graph represents a lagging schedule.

In an ideal situation the beginning is usually slow because people need to acquire confidence with the project, and once the schedule has achieved 20-30% of the work completed, 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.

What is the scenario before Time=0, i.e., before launching of the project?

In practice, most organizations don't really start from scratch when launching a project. Some pre-analysis work has been done in order to get an idea of what has to be done in terms of requirements, characteristics and resources needed for the project. With this information (although it's at high level), it's possible to make an estimation of the time and cost; decisions are usually taken after this information is available (or at least we reach a confidence level of 80%). The realization of a successful project will require commitments from the operating organization and all stakeholders.

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…