Cost Estimation Techniques for Projects
(→Introduction) |
|||
| (64 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | ''' | + | ''Developed by Nikolaos Gavriilidis'' |
| − | |||
| − | These techniques differ to each other, to the point that some | + | '''Cost estimation techniques''' are methods, used by project managers in order to calculate the total cost of a project before it even starts. How much the project will cost is a question that all stakeholders will make when they are being advised about the project. Therefore, it is important to make use of numerous techniques in order to estimate cost fast and accurately. |
| + | |||
| + | In this article, the most important techniques that project managers use in order to estimate the cost of a project are going to be analyzed. These techniques are, the expert judgment, the analogous estimate, the parametric estimate, the three point estimate, the bottom up estimate, the reserve analysis and the vendor bid analysis. | ||
| + | |||
| + | These techniques differ to each other, to the point that some of them require more time to estimate the cost, others are cheaper and some are more accurate. Project managers have to consider all possible parameters and use the appropriate technique for each specific project or a combination of techniques. | ||
==Introduction== | ==Introduction== | ||
| − | [[File:accuracy_of_estimating.jpg|thumb|right| | + | [[File:accuracy_of_estimating.jpg|thumb|right|250px|Figure 1: Accuracy of Estimating <ref name="Soft"/>]] |
| − | + | It is crucial for the project managers to estimate the cost of the project. This cost includes:<ref name="Usmani" /> | |
| − | *''the cost of human hours'' | + | *''the cost of human hours'' and in accordance necessary prior estimation of the duration of the project |
*''the cost of the equipment'' and | *''the cost of the equipment'' and | ||
*''the cost of materials'' that are required for the project, as well as any | *''the cost of materials'' that are required for the project, as well as any | ||
*''contingency cost''. | *''contingency cost''. | ||
| − | Estimating the cost of the project always | + | Estimating the cost of the project always includes a lot of uncertainty. This uncertainty derives from the fact that every project is unique, so the experience of the manager with similar projects plays important role. Generally, the bigger the size of the project, the more accuracy required but also the most difficult to achieve this accuracy. Moreover, planning horizon can affect the quality of estimation, meaning that the more distant the project is the less accurate the cost estimation. The complexity and the duration of the project can affect the uncertainty of the estimation too. The longer the duration of the project, the bigger the uncertainty for the cost estimation. Lastly, people involved with the project always come with an uncertainty, as for example if the members of a team have worked together before, they will need less time to start performing as a team.<ref name="ProjectMan" /> |
==Cost Estimation Techniques== | ==Cost Estimation Techniques== | ||
===Expert Judgment=== | ===Expert Judgment=== | ||
| − | This technique is one of the most quick and easy | + | This technique is one of the most quick and easy techniques to implement and requires no resources. It is mostly used at the very beginning, when there are no data available. It is based on the experience and knowledge the project manager has on this kind of project, and his ability to foresee things. If the manager is not so experienced he can still use the expert judgement of other people with hands on experience, but he has to make sure that they will have the same understanding for the project with him.<ref name="Kevin"/> |
| − | A disadvantage of this technique is that the manager may not be able to actually find an expert for the specific project and sometimes the expert may be biased for the project and make | + | A disadvantage of this technique is that the manager may not be able to actually find an expert for the specific project, and sometimes the expert may be biased for the project and make mistakes.<ref name="Guru" /> |
===Analogous Estimate=== | ===Analogous Estimate=== | ||
| − | In analogous estimating technique, the cost of the current project is estimated by comparing it with a similar project that has been already finished by the organization. The project manager has to use historical data in order to find the most relevant project that matches closely the profile of the current project. Since all the projects are unique, most of the times the manager has to make the necessary changes | + | In analogous estimating technique, the cost of the current project is estimated by comparing it with a similar project that has been already finished by the organization. The project manager has to use historical data in order to find the most relevant project that matches closely the profile of the current project. Since all the projects are unique, most of the times the manager has to make the necessary changes, so as to adjust the current cost estimation to the known differences of the two projects, thus he uses his expert judgement to this technique, too. <ref name="Usmani" /> |
| − | For example, a company that | + | For example, we assume that a company that develops webpages for other companies, has finished a web page in one month with cost of 5000 €. Now, the same company has to build a similar web page for another company, so they can estimate the same price and time for the new project. |
| − | This technique is also used at the beginning stages of a project when there is not much detail | + | This technique is also used at the beginning stages of a project when there is not much detail available. It can provide managers with fast results with low expenses, but its results are not very reliable and they are dependent on the existence of past projects in the same company. |
===Parametric Estimate=== | ===Parametric Estimate=== | ||
| Line 36: | Line 39: | ||
The parametric cost estimating technique except from historical data uses also statistical data from other projects. It uses the statistical data of the key cost driver parameters to estimate the cost of the new project. | The parametric cost estimating technique except from historical data uses also statistical data from other projects. It uses the statistical data of the key cost driver parameters to estimate the cost of the new project. | ||
| − | For example, a software company knows that the cost is 2 € per line of code. | + | For example, a software company knows that the cost is 2 € per line of code. Hence, if they estimate that the project will be around 5000 lines they can estimate a total cost of 10.000 €. Many projects have more than one key cost driver parameters that need to be taken into account. |
| − | This is a more scientific technique that provides more accurate results due to the use of average known rates. It is also fast and cheap but its accuracy relies on the quality of the data. If the statistical data are old or obsolete due to changes in the equipment for example, the results may not be accurate enough.<ref name="Chris"/> | + | This is a more scientific technique that provides more accurate results due to the use of average known rates. It is also fast and cheap, but its accuracy relies on the quality of the data. If the statistical data are old or obsolete due to changes in the equipment for example, the results may not be accurate enough.<ref name="Chris"/> |
===Three Point Estimate=== | ===Three Point Estimate=== | ||
| − | The three point estimating technique is used, in order to reduce as much as possible the uncertainties and risks. In this technique instead of making one cost estimation, the project manager has to make three different estimations, each one corresponding to one of the following estimate types:<ref name="Paul"/> | + | The three point estimating technique is used, in order to reduce as much as possible the uncertainties and risks. In this technique, instead of making one cost estimation, the project manager has to make three different estimations, each one corresponding to one of the following estimate types:<ref name="Paul"/> |
''Most Likely Cost (ML):'' This estimation considers that everything will be executed as usual and the project will run as planned. | ''Most Likely Cost (ML):'' This estimation considers that everything will be executed as usual and the project will run as planned. | ||
| Line 50: | Line 53: | ||
''Optimistic Cost (O):'' This estimation considers the best case scenario, assuming that everything will roll better than originally planned and the cost will be lower. | ''Optimistic Cost (O):'' This estimation considers the best case scenario, assuming that everything will roll better than originally planned and the cost will be lower. | ||
| − | After making these three estimations a weighted average of | + | After making these three estimations a weighted average of same is calculated. The most likely cost has a weight of 4, while the pessimistic and optimistic cost have a weight of 1. Therefore, the final estimated cost is calculated from the next formula: |
| Line 56: | Line 59: | ||
| − | For example, a renovation company knows that on average the most likely cost for the renovation of a house is 30.000 €. But if the house is in a very bad condition and needs changes also in the electricals and the water pipes the cost may reach up to 45.000 €. On the contrary, if the house is well preserved the cost | + | For example, a renovation company knows that on average the most likely cost for the renovation of a house is 30.000 €. But if the house is in a very bad condition and needs changes also in the electricals and the water pipes the cost may reach up to 45.000 €. On the contrary, if the house is well preserved the cost may only be 25.000 €. |
| + | |||
With the use of the above formula the company can estimate the cost as: | With the use of the above formula the company can estimate the cost as: | ||
| Line 63: | Line 67: | ||
| − | The three different estimations can be made | + | The three different estimations can be made by using other techniques that have already been described. The advantage of this technique is that it reduces the uncertainties and sets boundaries on the expectations. Moreover, when considering the worst and the best case scenario it becomes easier to provide a more accurate ''most likely scenario''. The disadvantages are that instead of one, the project manager has to make three estimations, which require more work and time, but still remain estimations that can be totally wrong. |
===Bottom Up Estimate=== | ===Bottom Up Estimate=== | ||
| − | This technique is used when | + | This technique is used when more accurate results are required. The project manager breaks down the project into small activities and estimates with great level of detail, the cost for each activity separately. The estimated cost of each activity at the bottom level is then rolled up, to calculate the overall cost of the project. The more detailed each activity is presented, the more accurate the result of the technique will be at the end.<ref name="Chris"/> |
| − | For example, a painting company | + | For example, a painting company intends to paint a house. First, they will have to separate the house to each room, measure the total surface of each wall and what color it needs to be painted. Then check the prices for each color and calculate the total cost of the paint. After that how much time is required for painting the whole house needs to be estimated, in order to calculate the labor hours. Finally, the specific equipment that is required for the job has to be defined precisely. |
| − | + | A disadvantage of this technique are that it requires the most time of all the techniques and the most money, as well. Especially for complex projects it can be very challenging to divide the project into small individual activities. Moreover, during the early stages, it may not be possible to perform this technique due to the lack of detail that might exist for the project. But despite all these, this technique provides the most accurate and reliable results of all the techniques.<ref name="Guru" /> | |
===Reserve Analysis=== | ===Reserve Analysis=== | ||
| − | When estimating the cost of a project it is reasonable to include some contingency reserves in order to account also any uncertainties that exist. These reserves may be a fixed number, a percentage of the estimated cost or even they can be calculated separately.<ref name="Paul"/> | + | When estimating the cost of a project it is reasonable to include some contingency reserves, in order to take into account also any uncertainties that exist. These reserves may be a fixed number, a percentage of the estimated cost or even they can be calculated separately.<ref name="Paul"/> |
| − | The manager can allocate the reserves in different points in order to establish buffers for some activities with high risks that can allow the smooth flow of the project. He can allocate them also in different phases of the project in order to match the delivery time as much as possible with the planned timetable. The amount of the reserves that is required for each project depends on the level of uncertainty for the projects. It is common to use reserves of 10% – 20% for projects with high risks and uncertainties while it may only require 0% - 5% for projects with low uncertainties. | + | The manager can allocate the reserves in different points, in order to establish buffers for some activities with high risks, that can allow the smooth flow of the project. He can allocate them also in different phases of the project, in order to match the delivery time as much as possible with the planned timetable. The amount of the reserves that is required for each project, depends on the level of uncertainty for the projects. It is common to use reserves of 10% – 20% for projects with high risks and uncertainties while it may only require 0% - 5% for projects with low uncertainties. |
| − | An example in which is necessary to make use of this method is the following. A software company that develops | + | An example in which it is necessary to make use of this method is the following. A software company that develops codes for its customers always aims to deliver a code without problems. But the manager knows that it is almost impossible to come up with a bug free code from the first time. Therefore, he has to estimate an amount of time and resources that are required in order to fix the bugs of the code. These bugs are not known from the beginning and they were not made intentionally, but by using the reserve analysis and taking into account the uncertainties, the manager can now consider them, too.<ref name="Guru" /> |
===Vendor Bid Analysis=== | ===Vendor Bid Analysis=== | ||
| − | The last technique is referred to specific cases when a product is provided by vendors or a service has been outsourced. When vendors exist the company can make a request for proposal to the vendors in order to estimate the cost for the specific product or service. The proposal is sent to some vendors that the company knows that | + | The last technique is referred to specific cases when a product is provided by vendors or a service has been outsourced. When vendors exist, the company can make a request for proposal to the vendors in order to estimate the cost for the specific product or service. The proposal is sent to some vendors that the company knows that are qualified and reliable for this kind of work. This request for proposal should describe the job in deep detail and the level of quality that is required, so that the vendors can make an accurate estimation. After the proposal is sent, it is the vendors’ job to do the cost estimation.<ref name="Saylor"/> |
Then the project manager collects all the responses from the vendors with the estimated cost and the duration. It is now his job to evaluate the proposals and determine the range of the cost for the service. | Then the project manager collects all the responses from the vendors with the estimated cost and the duration. It is now his job to evaluate the proposals and determine the range of the cost for the service. | ||
| − | An example of this technique is when a company wants to move its offices to another building but does not want to spend time on doing it on its own. At this case it can contact some transportation companies and ask them to give a proposal for the specific movement. After gathering their replies the project manager can decide which vendor fits best their requirements. | + | An example of this technique, is when a company wants to move its offices to another building but does not want to spend time on doing it on its own. At this case, it can contact some transportation companies and ask them to give a proposal for the specific movement. After gathering their replies the project manager can decide which vendor fits best their requirements. |
| − | The disadvantage of this method is that it relies on the capability and the knowledge of the vendors and the company does not gain any knowledge for future project estimation. On the other hand, all the job is done by the vendors so the company does not have to spend any resources in order to estimate the specific cost.<ref name="Chris"/> | + | The disadvantage of this method is that it relies on the capability and the knowledge of the vendors, and the company does not gain any knowledge for future project estimation. On the other hand, all the job is done by the vendors, so the company does not have to spend any resources in order to estimate the specific cost.<ref name="Chris"/> |
== Estimating Pitfalls== | == Estimating Pitfalls== | ||
| − | When making estimations there are some common pitfalls that project managers fall into. The most common | + | When making estimations there are some common pitfalls that project managers fall into. The most common are the following:<ref name="Gary"/> |
*'''Insufficient defined scope of project:''' This can occur when the project is not broken down far enough or some works have been misinterpreted. | *'''Insufficient defined scope of project:''' This can occur when the project is not broken down far enough or some works have been misinterpreted. | ||
| Line 99: | Line 103: | ||
*'''Omissions:''' This happens when the estimator forgets to take into account important things that may result in different final cost. | *'''Omissions:''' This happens when the estimator forgets to take into account important things that may result in different final cost. | ||
| − | *'''Rampant optimism:''' It occurs when in the estimation | + | *'''Rampant optimism:''' It occurs when in the estimation only the best case scenario is considered. |
*'''Failure to conclude risks and uncertainty:''' Ignoring the risks and uncertainties of the project, can lead to a very false estimation. | *'''Failure to conclude risks and uncertainty:''' Ignoring the risks and uncertainties of the project, can lead to a very false estimation. | ||
| Line 111: | Line 115: | ||
==Application== | ==Application== | ||
| − | [[File: | + | [[File:comparison.PNG|thumb|right|500px|Figure 2: Comparing the Cost Estimation Techniques]] |
| + | |||
| + | The big question now is which cost estimation technique should a manager use. The point is that there is not a technique that is better than the others in all the aspects. Hence, the project manager has to consider some parameters first in order to decide which technique to use. | ||
| + | |||
| + | The first criteria that the manager has to consider, is in which phase of the project they currently are. | ||
| + | At early stages of the project, there is lack of details and information about it, thus the manager has to use one of the top down techniques like the ''expert judgement'', the ''analogous estimate'' or the ''parametric estimate'', if he has access to statistical data. | ||
| + | In later stages, when the project is defined with details, he can use a ''bottom up'' technique in order to gain more accurate results. | ||
| + | |||
| + | Other criteria is the level accuracy required for the estimation. There are some projects that additional accuracy in the estimation will not make any difference, so the manager can use one of the top down techniques. The accuracy is also analogue to the cost and time spent for the estimation. The more accurate a method is, the more expensive and time consuming it is. Therefore, the manager has to consider if it will add any value by making a more accurate estimation, or he will add only cost and time to the project. | ||
| + | |||
| + | Lastly, the manager has to recognize the amount of uncertainty existing in the project. If there is too much uncertainty, a ''reserve analysis'' is mandatory and a ''top down'' technique will provide a better perception of the total cost. On the other hand, while the project continues, the uncertainties are getting smaller and a ''bottom up'' technique can be used for accurate results. | ||
| + | |||
| + | If there are important vendors in the project, a ''vendor bid analysis'' would be very useful. | ||
| + | |||
| + | In conclusion, only one estimation technique will not give the best result all the times. Hence, the project manager has to consider using a combination, so that each one fits better his requirement for each specific phase of the project. | ||
| + | |||
| + | ==Annotated Bibliography== | ||
| − | + | *'''Paul Newton (2015), ''Managing the Project Budget, Project Skills''.''' <ref name="Paul"/> | |
| − | + | ''Summary:'' This book describes how to manage your budget when you take over a project. At the beginning, it provides information concerning how a manager can estimate the cost of a project, in order to set the budget. Then it describes how to manage the cost during the project, thus it will remain inside the budget that has been set. | |
| − | |||
| − | |||
| − | |||
| − | + | *'''Gary R. Heerkens, PMP (2002), ''Project Management''.'''<ref name="Gary"/> | |
| − | + | ''Summary:'' This book describes project management tools and techniques used during the entire project management process. But instead of providing information only about their proper use, it describes also the principles behind their use. Thus, project managers can understand both how and why they need to do things. | |
| − | |||
| − | + | *'''Saylor Foundation, ''Project Management in a Complex World''.''' <ref name="Saylor"/> | |
| − | + | ''Summary:'' This book provides an overview of project management and introduces the challenges that come with project complexity. It provides also a tool for profiling a project based on the complexity, and describes the different project management approaches for each project profile. | |
==References== | ==References== | ||
<references> | <references> | ||
| − | <ref name="Usmani"> Fahad Usmani (2012) ''4 Tools to Estimate Cost in the Project Management.'' [online] pmstudycircle.com. Available at: https://pmstudycircle.com/2012/06/4-tools-to-estimate-costs-in-the-project-management/ [Accessed 15 Sep. 2016] ''Summary:'' This article describes four tools for doing | + | <ref name="Usmani"> Fahad Usmani (2012) ''4 Tools to Estimate Cost in the Project Management.'' [online] pmstudycircle.com. Available at: https://pmstudycircle.com/2012/06/4-tools-to-estimate-costs-in-the-project-management/ [Accessed 15 Sep. 2016] ''Summary:'' This article describes four tools for doing cost estimation in the project management area.</ref> |
<ref name="ProjectMan"> Erik W. Larson and Clifford F. Gray (2011) ''Project Management the managerial process'', 5th edition. McGraw-Hill Companies, p.128-129 ''Summary:'' This book describes the hole process of managing a project.</ref> | <ref name="ProjectMan"> Erik W. Larson and Clifford F. Gray (2011) ''Project Management the managerial process'', 5th edition. McGraw-Hill Companies, p.128-129 ''Summary:'' This book describes the hole process of managing a project.</ref> | ||
| Line 144: | Line 160: | ||
<ref name="Chris"> Chris O'Halloran (2013) ''Improving Project Estimation Accuracy.'' [online] strikingprojectmanagement.com. Available at: http://strikingprojectmanagement.com/project-estimation/ [Accessed 15 Sep. 2016] ''Summary:'' This article describes how to improve your estimation accuracy in projects by using specific techniques.</ref> | <ref name="Chris"> Chris O'Halloran (2013) ''Improving Project Estimation Accuracy.'' [online] strikingprojectmanagement.com. Available at: http://strikingprojectmanagement.com/project-estimation/ [Accessed 15 Sep. 2016] ''Summary:'' This article describes how to improve your estimation accuracy in projects by using specific techniques.</ref> | ||
| − | <ref name="Paul"> Paul Newton (2015) ''Managing the Project Budget, Project Skills''. free-management-ebooks, p.14-19 ''Summary:'' This book describes how to manage your budget when you take over a project.</ref> | + | <ref name="Paul"> Paul Newton (2015) ''Managing the Project Budget, Project Skills''. free-management-ebooks, ISBN: 978-1-62620-982-9, p.14-19 ''Summary:'' This book describes how to manage your budget when you take over a project.</ref> |
<ref name="Saylor"> Saylor Foundation ''Project Management in a Complex World''. http://www.saylor.org/books/, under the Creative Commons | <ref name="Saylor"> Saylor Foundation ''Project Management in a Complex World''. http://www.saylor.org/books/, under the Creative Commons | ||
Attribution-NonCommercial-ShareAlike 3.0 License, p.279-284 ''Summary:'' This book provides an overview of project management and introduces the challenges that come with project complexity.</ref> | Attribution-NonCommercial-ShareAlike 3.0 License, p.279-284 ''Summary:'' This book provides an overview of project management and introduces the challenges that come with project complexity.</ref> | ||
| − | <ref name="Gary"> Gary R. Heerkens, PMP (2002) ''Project Management''. McGraw-Hill Companies, p.109-110 ''Summary:'' This book describes the | + | <ref name="Gary"> Gary R. Heerkens, PMP (2002) ''Project Management''. McGraw-Hill Companies, ISBN:0-07-139449-4, p.109-110 ''Summary:'' This book describes project management tools and techniques used during the entire project management process.</ref> |
| − | <ref name="Soft"> http://www.softwaremetrics.com/Articles/estimating.htm ''Summary:'' This site develops estimating software.</ref> | + | <ref name="Soft"> http://www.softwaremetrics.com/Articles/estimating.htm [Accessed 15 Sep. 2016] ''Summary:'' This site develops estimating software.</ref> |
</references> | </references> | ||
Latest revision as of 14:57, 18 December 2018
Developed by Nikolaos Gavriilidis
Cost estimation techniques are methods, used by project managers in order to calculate the total cost of a project before it even starts. How much the project will cost is a question that all stakeholders will make when they are being advised about the project. Therefore, it is important to make use of numerous techniques in order to estimate cost fast and accurately.
In this article, the most important techniques that project managers use in order to estimate the cost of a project are going to be analyzed. These techniques are, the expert judgment, the analogous estimate, the parametric estimate, the three point estimate, the bottom up estimate, the reserve analysis and the vendor bid analysis.
These techniques differ to each other, to the point that some of them require more time to estimate the cost, others are cheaper and some are more accurate. Project managers have to consider all possible parameters and use the appropriate technique for each specific project or a combination of techniques.
Contents |
[edit] Introduction
It is crucial for the project managers to estimate the cost of the project. This cost includes:[2]
- the cost of human hours and in accordance necessary prior estimation of the duration of the project
- the cost of the equipment and
- the cost of materials that are required for the project, as well as any
- contingency cost.
Estimating the cost of the project always includes a lot of uncertainty. This uncertainty derives from the fact that every project is unique, so the experience of the manager with similar projects plays important role. Generally, the bigger the size of the project, the more accuracy required but also the most difficult to achieve this accuracy. Moreover, planning horizon can affect the quality of estimation, meaning that the more distant the project is the less accurate the cost estimation. The complexity and the duration of the project can affect the uncertainty of the estimation too. The longer the duration of the project, the bigger the uncertainty for the cost estimation. Lastly, people involved with the project always come with an uncertainty, as for example if the members of a team have worked together before, they will need less time to start performing as a team.[3]
[edit] Cost Estimation Techniques
[edit] Expert Judgment
This technique is one of the most quick and easy techniques to implement and requires no resources. It is mostly used at the very beginning, when there are no data available. It is based on the experience and knowledge the project manager has on this kind of project, and his ability to foresee things. If the manager is not so experienced he can still use the expert judgement of other people with hands on experience, but he has to make sure that they will have the same understanding for the project with him.[4]
A disadvantage of this technique is that the manager may not be able to actually find an expert for the specific project, and sometimes the expert may be biased for the project and make mistakes.[5]
[edit] Analogous Estimate
In analogous estimating technique, the cost of the current project is estimated by comparing it with a similar project that has been already finished by the organization. The project manager has to use historical data in order to find the most relevant project that matches closely the profile of the current project. Since all the projects are unique, most of the times the manager has to make the necessary changes, so as to adjust the current cost estimation to the known differences of the two projects, thus he uses his expert judgement to this technique, too. [2]
For example, we assume that a company that develops webpages for other companies, has finished a web page in one month with cost of 5000 €. Now, the same company has to build a similar web page for another company, so they can estimate the same price and time for the new project.
This technique is also used at the beginning stages of a project when there is not much detail available. It can provide managers with fast results with low expenses, but its results are not very reliable and they are dependent on the existence of past projects in the same company.
[edit] Parametric Estimate
The parametric cost estimating technique except from historical data uses also statistical data from other projects. It uses the statistical data of the key cost driver parameters to estimate the cost of the new project.
For example, a software company knows that the cost is 2 € per line of code. Hence, if they estimate that the project will be around 5000 lines they can estimate a total cost of 10.000 €. Many projects have more than one key cost driver parameters that need to be taken into account.
This is a more scientific technique that provides more accurate results due to the use of average known rates. It is also fast and cheap, but its accuracy relies on the quality of the data. If the statistical data are old or obsolete due to changes in the equipment for example, the results may not be accurate enough.[6]
[edit] Three Point Estimate
The three point estimating technique is used, in order to reduce as much as possible the uncertainties and risks. In this technique, instead of making one cost estimation, the project manager has to make three different estimations, each one corresponding to one of the following estimate types:[7]
Most Likely Cost (ML): This estimation considers that everything will be executed as usual and the project will run as planned.
Pessimistic Cost (P): This estimation considers the worst case scenario, when everything will go wrong and the cost will be greater than usual.
Optimistic Cost (O): This estimation considers the best case scenario, assuming that everything will roll better than originally planned and the cost will be lower.
After making these three estimations a weighted average of same is calculated. The most likely cost has a weight of 4, while the pessimistic and optimistic cost have a weight of 1. Therefore, the final estimated cost is calculated from the next formula:
For example, a renovation company knows that on average the most likely cost for the renovation of a house is 30.000 €. But if the house is in a very bad condition and needs changes also in the electricals and the water pipes the cost may reach up to 45.000 €. On the contrary, if the house is well preserved the cost may only be 25.000 €.
With the use of the above formula the company can estimate the cost as:
€
The three different estimations can be made by using other techniques that have already been described. The advantage of this technique is that it reduces the uncertainties and sets boundaries on the expectations. Moreover, when considering the worst and the best case scenario it becomes easier to provide a more accurate most likely scenario. The disadvantages are that instead of one, the project manager has to make three estimations, which require more work and time, but still remain estimations that can be totally wrong.
[edit] Bottom Up Estimate
This technique is used when more accurate results are required. The project manager breaks down the project into small activities and estimates with great level of detail, the cost for each activity separately. The estimated cost of each activity at the bottom level is then rolled up, to calculate the overall cost of the project. The more detailed each activity is presented, the more accurate the result of the technique will be at the end.[6]
For example, a painting company intends to paint a house. First, they will have to separate the house to each room, measure the total surface of each wall and what color it needs to be painted. Then check the prices for each color and calculate the total cost of the paint. After that how much time is required for painting the whole house needs to be estimated, in order to calculate the labor hours. Finally, the specific equipment that is required for the job has to be defined precisely.
A disadvantage of this technique are that it requires the most time of all the techniques and the most money, as well. Especially for complex projects it can be very challenging to divide the project into small individual activities. Moreover, during the early stages, it may not be possible to perform this technique due to the lack of detail that might exist for the project. But despite all these, this technique provides the most accurate and reliable results of all the techniques.[5]
[edit] Reserve Analysis
When estimating the cost of a project it is reasonable to include some contingency reserves, in order to take into account also any uncertainties that exist. These reserves may be a fixed number, a percentage of the estimated cost or even they can be calculated separately.[7]
The manager can allocate the reserves in different points, in order to establish buffers for some activities with high risks, that can allow the smooth flow of the project. He can allocate them also in different phases of the project, in order to match the delivery time as much as possible with the planned timetable. The amount of the reserves that is required for each project, depends on the level of uncertainty for the projects. It is common to use reserves of 10% – 20% for projects with high risks and uncertainties while it may only require 0% - 5% for projects with low uncertainties.
An example in which it is necessary to make use of this method is the following. A software company that develops codes for its customers always aims to deliver a code without problems. But the manager knows that it is almost impossible to come up with a bug free code from the first time. Therefore, he has to estimate an amount of time and resources that are required in order to fix the bugs of the code. These bugs are not known from the beginning and they were not made intentionally, but by using the reserve analysis and taking into account the uncertainties, the manager can now consider them, too.[5]
[edit] Vendor Bid Analysis
The last technique is referred to specific cases when a product is provided by vendors or a service has been outsourced. When vendors exist, the company can make a request for proposal to the vendors in order to estimate the cost for the specific product or service. The proposal is sent to some vendors that the company knows that are qualified and reliable for this kind of work. This request for proposal should describe the job in deep detail and the level of quality that is required, so that the vendors can make an accurate estimation. After the proposal is sent, it is the vendors’ job to do the cost estimation.[8]
Then the project manager collects all the responses from the vendors with the estimated cost and the duration. It is now his job to evaluate the proposals and determine the range of the cost for the service.
An example of this technique, is when a company wants to move its offices to another building but does not want to spend time on doing it on its own. At this case, it can contact some transportation companies and ask them to give a proposal for the specific movement. After gathering their replies the project manager can decide which vendor fits best their requirements.
The disadvantage of this method is that it relies on the capability and the knowledge of the vendors, and the company does not gain any knowledge for future project estimation. On the other hand, all the job is done by the vendors, so the company does not have to spend any resources in order to estimate the specific cost.[6]
[edit] Estimating Pitfalls
When making estimations there are some common pitfalls that project managers fall into. The most common are the following:[9]
- Insufficient defined scope of project: This can occur when the project is not broken down far enough or some works have been misinterpreted.
- Omissions: This happens when the estimator forgets to take into account important things that may result in different final cost.
- Rampant optimism: It occurs when in the estimation only the best case scenario is considered.
- Failure to conclude risks and uncertainty: Ignoring the risks and uncertainties of the project, can lead to a very false estimation.
- Time pressure: Most of the times the project managers are working under strict deadlines that can lead to mistakes in the cost estimation.
- External pressure: Moreover many times they are told to achieve specific cost, timeline and quality that may be unrealistic.
- Estimator and task performer fail to communicate: When the estimator and the task performer are two different persons they may have different level of skills or different view for the task that might lead to problems.
[edit] Application
The big question now is which cost estimation technique should a manager use. The point is that there is not a technique that is better than the others in all the aspects. Hence, the project manager has to consider some parameters first in order to decide which technique to use.
The first criteria that the manager has to consider, is in which phase of the project they currently are. At early stages of the project, there is lack of details and information about it, thus the manager has to use one of the top down techniques like the expert judgement, the analogous estimate or the parametric estimate, if he has access to statistical data. In later stages, when the project is defined with details, he can use a bottom up technique in order to gain more accurate results.
Other criteria is the level accuracy required for the estimation. There are some projects that additional accuracy in the estimation will not make any difference, so the manager can use one of the top down techniques. The accuracy is also analogue to the cost and time spent for the estimation. The more accurate a method is, the more expensive and time consuming it is. Therefore, the manager has to consider if it will add any value by making a more accurate estimation, or he will add only cost and time to the project.
Lastly, the manager has to recognize the amount of uncertainty existing in the project. If there is too much uncertainty, a reserve analysis is mandatory and a top down technique will provide a better perception of the total cost. On the other hand, while the project continues, the uncertainties are getting smaller and a bottom up technique can be used for accurate results.
If there are important vendors in the project, a vendor bid analysis would be very useful.
In conclusion, only one estimation technique will not give the best result all the times. Hence, the project manager has to consider using a combination, so that each one fits better his requirement for each specific phase of the project.
[edit] Annotated Bibliography
- Paul Newton (2015), Managing the Project Budget, Project Skills. [7]
Summary: This book describes how to manage your budget when you take over a project. At the beginning, it provides information concerning how a manager can estimate the cost of a project, in order to set the budget. Then it describes how to manage the cost during the project, thus it will remain inside the budget that has been set.
- Gary R. Heerkens, PMP (2002), Project Management.[9]
Summary: This book describes project management tools and techniques used during the entire project management process. But instead of providing information only about their proper use, it describes also the principles behind their use. Thus, project managers can understand both how and why they need to do things.
- Saylor Foundation, Project Management in a Complex World. [8]
Summary: This book provides an overview of project management and introduces the challenges that come with project complexity. It provides also a tool for profiling a project based on the complexity, and describes the different project management approaches for each project profile.
[edit] References
- ↑ http://www.softwaremetrics.com/Articles/estimating.htm [Accessed 15 Sep. 2016] Summary: This site develops estimating software.
- ↑ 2.0 2.1 Fahad Usmani (2012) 4 Tools to Estimate Cost in the Project Management. [online] pmstudycircle.com. Available at: https://pmstudycircle.com/2012/06/4-tools-to-estimate-costs-in-the-project-management/ [Accessed 15 Sep. 2016] Summary: This article describes four tools for doing cost estimation in the project management area.
- ↑ Erik W. Larson and Clifford F. Gray (2011) Project Management the managerial process, 5th edition. McGraw-Hill Companies, p.128-129 Summary: This book describes the hole process of managing a project.
- ↑ Kevin Crump (2015) 5 Methods of Project Estimation. [online] liquidplanner.com. Available at: https://www.liquidplanner.com/blog/5-methods-of-project-estimation/ [Accessed 15 Sep. 2016] Summary: This article describes five methods for doing estimation for projects.
- ↑ 5.0 5.1 5.2 Ray Sheen (2009) Project Management Estimating Tools & Techniques. [online] projectmanagementguru.com. Available at: http://www.projectmanagementguru.com/estimating.html [Accessed 15 Sep. 2016] Summary: This article describes tools and techniques that are used for estimation in the project management area.
- ↑ 6.0 6.1 6.2 Chris O'Halloran (2013) Improving Project Estimation Accuracy. [online] strikingprojectmanagement.com. Available at: http://strikingprojectmanagement.com/project-estimation/ [Accessed 15 Sep. 2016] Summary: This article describes how to improve your estimation accuracy in projects by using specific techniques.
- ↑ 7.0 7.1 7.2 Paul Newton (2015) Managing the Project Budget, Project Skills. free-management-ebooks, ISBN: 978-1-62620-982-9, p.14-19 Summary: This book describes how to manage your budget when you take over a project.
- ↑ 8.0 8.1 Saylor Foundation Project Management in a Complex World. http://www.saylor.org/books/, under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License, p.279-284 Summary: This book provides an overview of project management and introduces the challenges that come with project complexity.
- ↑ 9.0 9.1 Gary R. Heerkens, PMP (2002) Project Management. McGraw-Hill Companies, ISBN:0-07-139449-4, p.109-110 Summary: This book describes project management tools and techniques used during the entire project management process.
