Estimation Techniques

From apppm
(Difference between revisions)
Jump to: navigation, search
(→‎Limitations)
(→‎References)
Line 227: Line 227:
 
<ref name="five"> B. Flyvbjerg - Estimating Cost of a Project: Techniques and Examples,” Available online: https://towardsdatascience.com/the-iron-law-of-megaprojects-18b886590f0b </ref>
 
<ref name="five"> B. Flyvbjerg - Estimating Cost of a Project: Techniques and Examples,” Available online: https://towardsdatascience.com/the-iron-law-of-megaprojects-18b886590f0b </ref>
  
−
<ref name="seven"> Project Management: "Managing Successful Projects with PRINCE2" 6th Edition (2017) Chapter 9.4 pp 116-118,”
+
<ref name="seven"> Project Management: "Managing Successful Projects with PRINCE2" 6th Edition (2017) Chapter 9.4 pp 116-118,”</ref>
−
</ref>
+
 
 +
<ref name="four"> Methods of Cost Estimation in Projects – Tools and Techniques,” Available online: https://theconstructor.org/construction/methods-cost-estimation/36532/ </ref>
 +
 
  
  

Revision as of 11:54, 8 May 2023

Contents

Abstract

Estimations are a crucial part of project management, providing critical information to help project managers plan, execute, and control projects effectively. Project estimations help to identify the scope and requirements of a project, allocate resources, set realistic timelines, and develop budgets. They provide a roadmap for the project team to follow, helping to ensure that the project is completed on time, within budget and to the required level of quality.

Accurate estimations are essential for effective project management, allowing project managers to identify potential risks and challenges early on and to develop strategies to mitigate them. They also enable stakeholders to make informed decisions about whether to proceed with a project, how to allocate resources, and how to manage any potential risks or challenges that may arise.

Effective estimation requires a combination of experience, skill, and data analysis. Project managers must be able to assess the requirements of a project, understand the capabilities of the team, and factor in potential risks and uncertainties. They must also be able to use historical data and industry benchmarks to make informed estimates and track progress against these estimates throughout the project lifecycle.

In short, estimations are a critical component of successful project management, providing the foundation for planning, executing, and controlling projects effectively. Accurate estimations help to ensure that projects are completed on time, within budget, and to the required level of quality, helping organizations to achieve their goals and objectives.

The objective of this article is to create an understanding for the reader of what top-down and ground-up estimations are, what different techniques there exists and when and how they should be applied.

The Big Idea

The big idea behind top-down and bottom-up estimations is that they are two different approaches to estimating the size, scope, and cost or time of a project or initiative.

Top-down estimation involves starting with an overall estimate for the project and then breaking it down into smaller components. This approach is often used when there is limited information available about the project or when there is a need for a quick, high-level estimate. Top-down estimation can be useful for setting initial goals and identifying potential risks, but it may not provide a detailed understanding of the project's requirements and may not be accurate enough for budgeting and planning purposes.

Ground-up estimations, on the other hand, involves breaking down the project into smaller, more manageable components and estimating the time, effort, and resources required for each of these components. Ground-up estimations are therefore often performed when the work breakdown structure has been performed. This approach is often used when there is more detailed information available about the project and when a more accurate estimate is needed. Ground-up estimation can be time-consuming, but it can provide a more accurate understanding of the project's requirements and can be useful for budgeting and planning purposes.

Both approaches have their advantages and disadvantages, and the choice of which to use will depend on the specific needs of the project and the available information. In some cases, a combination of top-down and bottom-up estimation may be used to provide a more comprehensive estimate.

Top-down estimations

Top-down estimating is a project management technique that involves estimating the total cost or duration of a project without using detailed information or analysis. It starts with evaluating a projects budget, duration or scope as a whole and then separating it into smaller components[1]. It is often used by company leadership and project managers. Used techniques often include expert judgment, analogous estimating and historical data from similar projects to make an educated guess of the overall cost or duration of the project [2]. The estimate is based on the information available at the start of the project, hence the tasks in the work breakdown structure are not clearly defined yet. In top-down estimations, the first step is for the project manager to identify the major deliverables or expenses that are required to complete the project. Then, using their experience, expert judgement or historical data, they estimate the total cost or duration of the project. The expert judgement can be internally in the form of experienced managers and sometimes externally as outside experts. The top-down estimation priorities efficiency as it does not need middle management to provide detailed cost break downs, which allows managers to quickly asses potential opportunities, costs and duration. It can also be used for projects with a high degree of uncertainty or when there is a limited information available. However, it is important to note that top-down estimating is less accurate than ground-up estimating, which involves estimating the cost or duration of each individual task in the project, thus top-down is used in the beginning of the project. As a result of the inaccuracy associated with top-down estimations multiple techniques exist to assist in minimizing the error here among consensus method, ratio method and apportion method.

Ground-up estimations

Ground-up estimating or bottom-up estimating is a project estimation technique that involves breaking down the project into smaller, more manageable components, and estimating the effort, duration, or cost required for each of these components individually. These estimates are then aggregated to arrive at an overall estimate for the project [1]. An example of applying ground-up estimating could involve estimating the effort required to develop a new software application. The project could be broken down into smaller tasks, such as designing the user interface, coding the application, testing the application, and deploying the application. The effort required for each task would then be estimated individually, and the estimates would be aggregated to arrive at an overall estimate for the project. Based on the level of detail ground-up estimating is more accurate than top-down estimating because it provides a detailed breakdown of the project cost or duration. This makes it easier to identify specific areas where costs or timelines may need to be adjusted. Ground-up estimating is often used in later stages of a project when the level of detail required for a ground-up estimate is available.

Figure 2: Ground-up level durations costs [3]


Some advantages of the ground-up approach includes:

  • It provides a detailed estimate of the project, which can help to identify potential risks and dependencies.
  • It allows for a more accurate estimate of the project, as each component is estimated individually based on its specific requirements and characteristics.
  • It provides a transparent and verifiable estimate, as each component estimate can be validated and adjusted based on historical data or expert judgment.

However, as ground-up estimations sound accurate and efficient compared to top-down it also has its limitations including:

  • It can be time-consuming and resource-intensive to estimate each component individually.
  • It may not be appropriate for projects with a high level of uncertainty or complexity, as it may be difficult to estimate each component accurately.
  • It may be difficult to communicate the estimate to stakeholders, as the level of detail may be overwhelming or difficult to understand.

In summary bottom-up estimating is a detailed project estimation technique that can provide a more accurate and transparent estimate of the project. However, it may not be appropriate for all projects and may require more time and resources than other estimation techniques such as top-down.

Estimation techniques and their application

In summary top-down is a high-level approach that is used when limited information is available whereas ground-up is a detailed approach where estimating the cost or duration of each work package at the lowest possible level, and then aggregating the estimates to produce a total cost or duration for the project. These approaches do not alone help in finding a sufficient or accurate estimate and multiple methods therefore exist in order to help estimations become as accurate as possible. Whereas, some methods are mainly made for top-down estimating and other ground-up estimating some can be applied at both levels.

Expert Judgement

Expert judgement is a commonly used method in project management for estimating activity durations and costs. It involves seeking input and guidance from individuals or teams with relevant experience and expertise to develop more accurate and reliable estimates. Expert judgement can be particularly useful in situations where historical data or other estimation methods are not available or reliable, or when there is a high degree of uncertainty or complexity involved in the activity being estimated. It can also help identify potential problems or risks that may impact the duration of an activity and develop contingency plans to address them.

Expert judgement can be in the form of project team members, stakeholders, industry experts, and consultants. It is important to seek input from a diverse range of experts to ensure a comprehensive and balanced perspective on the activity being estimated. Expert judgement can be applied or used in multiple ways and it is often seen both in top down and ground-up in the following ways:

  • In the beginning of a project the estimations are often performed top-down due to the lack of team members and other estimation techniques might not be available due to the lack of data.
  • With a ground-up approach having generated the deliverables for the WBS by asking those responsible for each work task about their estimates on resource requirements. This type of expert judgement can lead to very accurate results.

However, expert judgement does have limitations. It may be subject to bias or personal opinions, and the accuracy of the estimate depends on the expertise and experience of the individuals providing the judgement. Furtmore, it can be costly from hiring experts and if other methods such as the delphi/consensus method is applied it can also be time consuming as it becomes a repetitive process where experts must agree on the estimations. Anyhow, it has its advantages as it is a quick and efficient method that can be easily applied and does not require historical data.

Analogous Estimating

Analogous estimating is a project estimation technique that uses historical data or expert judgment to estimate the parameters of a new project [4]. It is a top-down approach to estimating, as it relies on the assumption that the current project is similar in scope, complexity, and requirements to past projects, and that historical data can be used to derive estimates for the current project. An example of analogous estimating might involve estimating the cost of a new construction project based on the cost of a similar construction project completed in the past. The historical data would be used to identify the key cost drivers of the previous project, and these drivers would be applied to the current project to derive an estimate of its cost.

Some advantages of applying analogous estimating is:

  • Quick and easy way to estimate the parameters of a new project, as it relies on historical data or expert judgment rather than a detailed analysis of the project requirements.
  • It can provide a rough estimate of the project parameters early in the project lifecycle, which can be useful for budgeting and resource allocation purposes.
  • It can be used in situations where there is limited information about the project requirements or where a detailed analysis of the requirements is not feasible.

However, this method also has its limitations in the form of:

  • It may not be as accurate as other estimation techniques, such as bottom-up estimating or parametric modeling, which are based on a more detailed analysis of the specific requirements of the project.
  • Not useful for projects that are significantly different from past projects, as the historical data will not be relevant or applicable.
  • Relies heavily on the expertise of the estimator, which can introduce bias and subjectivity into the estimates.

Three-point Estimation

As known from the iron law of mega projects the larger a project the more likely it is to exceed budget, schedule and quality. From the iron law of mega projects Bent Flyvbjerg mentions “Nine out of ten such projects have cost overruns. Overruns of up to 50 percent in real terms are common, over 50 percent not uncommon”[5]. This is where three point estimating comes into the picture trying to prevent overruns from happening by estimating the duration or cost of a project or a task using three estimates: an optimistic estimate, a pessimistic estimate, and a most likely estimate. Thereby this estimation technique also includes the possibility of the project being over time, budget or quality. Even though this technique includes the pessimistic scenario it also includes an optimistic scenario which could balance the calculation to be closer to the anticipated most likely scenario [1].

  • The optimistic estimate represents the best-case scenario for completing a task. It assumes that everything will go smoothly and that no unexpected issues will arise.
  • The pessimistic estimate represents the worst-case scenario, assuming that everything that could go wrong will go wrong.
  • The most likely estimate is the estimate that is based on the most realistic assessment of the task, taking into account the risks and uncertainties.

This technique is commonly used in project management to account for the uncertainties and risks associated with a project.

When performing a three point estimate, the project manager typically gathers input from experts, stakeholders, and team members who have experience with similar tasks. The final estimation of duration or cost can then be calculated in two different ways[3]:

  • The triangular distribution, which calculates the average of the optimistic, pessimistic and most likely estimate. This is calculated in the following way where O=optimistic, P=pessimistic and M=most likely: (O+P+M)/3


  • The PERT distribution where a weighted average is calculated. The PERT distribution relies on the assumption that the probability of the most likely estimate is greater than the pessimistic and optimistic estimates and it is therefore assigned a four times larger value than the others. The PERT distribution is calculated the following way: (O + 4*M + P) / 6

Parametric estimations

Parametric estimating is a method used in project management to estimate the duration of an activity based on statistical models and a set of parameters or variables [4]. It involves identifying the key variables that impact the duration of an activity and using historical data to develop statistical models or formulas to estimate future durations or costs [1]. This method is particularly useful for activities that are well-defined and have a high degree of standardization. By measuring the impact of different variables and assessing their interdependencies, project managers can develop more accurate and reliable estimates, reducing the risk of schedule overruns. Parametric estimating can also help identify potential problems or challenges that may impact the duration of an activity. An example of applying parametric estimating could be a construction company sector using a cost per square foot to estimate the cost of a building project. This method involves determining the average cost per square foot of similar construction projects in the same geographical area and using this information to estimate the cost of the project. If a construction company were to build a new building with a total floor area of 50,000 square feet. The company make use of historical data from similar projects in the same location to estimate the cost per square foot. If the average cost per square foot for similar projects is $200, then the estimated cost for the new office building would be $200 * 50,000 = $10,000,000.

An advantage of the parametric estimating is that it can be accurate for a project similar to a prior but it may not be effective for activities that are unique or have a high degree of variability, as the impact of different variables may be difficult to measure and predict. Additionally, the accuracy of parametric estimates depends on the quality and availability of historical data, which may be limited in some cases. This method can be applied when using top-down estimations where the overall cost or duration is calculated for the entire project as well as ground-up estimations where the parametric estimations are calculated for each work package.

Limitations

Figure 2: Quick overview of estimation techniques [3]

NOT DONE YET

  • Summarize the limitations of the top-down and ground-up estimating
  • Limitations of the described methods within this field and why some are or are not suited for top-down or ground-up.
  • Show table from source that compares these methods in a matrix.


Analogous Estimating
Bottom-up Estimating
Parametric Estimating
Expert Judgment
Three-Point Estimating

Input Data
[3]
Data from previous comparable

projects
Activities & their scope of labour
Data from previous comparable
projects
The professionals' knowledge
and experience
Different techniques for estimating
costs

Method 		Using data of past similar
projects & adapting it
 Estimating costs at the lowest
possible detail, then summing up
the different components
 Using data of past projects the
present project's cost per parameter unit.
 Experts provide estimates of the
resources required to perform the
job within the scope of the project,
either from the top-down or from
the bottom-up. 		An optimistic, pessimistic, and most
probable estimate is produced using one of
the four other approaches
and are then based on the Pert distribution or triangular
converted into a weighted average value .

Output Type
Total cost of the project, as well
as a cost of each activity
Total cost of the project, as well
as a cost of each activity
Total cost of the project, as well
as a cost of each activity
Varies from each project, but
often times several outputs
Improved estimates of costs,
aswell as the standard deviation
of those costs
Limitations Risk of being inaccurate as a result of being a top-down estimations
Mostly used in the beginning
of a project 		Does not address for the
ressources required for
combining each activity 		Requires historical data which is both
time consuming to gather and may
not always be available 		Expensive & time consuming Time consuming to provide an estimate
for three scenarios

Conclusion

  • Conclude when top-down and ground up should be used
  • Is there a smart way of combining them, the more a project evolves the more detailed information available.
  • What about the mentioned techniques?
  • why do we use these techniques - failure of projects and estimations are important but why?
  • Important to mention is that there has only been found limited information online on actual top-down approaches and ground-up approaches and therefore the different estimation techniques that can help in order to make estimates more accurate have been chosen to be investigated I will therefore have to have a talk with the teachers if this is actually the purpose of this article or what my point of view should be

Annotated bibliography

Top-down:

https://www.indeed.com/career-advice/career-development/top-down-estimating


Expert Judgement:

https://asana.com/resources/expert-judgment

https://project-management.info/estimating-activity-durations/#6-expert-judgement

https://project-management.info/estimating-project-cost/#8-expert-judgment-


Analogous estimating

https://project-management.info/analogous-estimating/

https://project-management.info/estimating-project-cost/#8-expert-judgment-

https://www.indeed.com/career-advice/career-development/analogous-estimating


Ground-up: https://project-management.info/bottom-up-estimating-definition-example-pros-cons/

http://wiki.doing-projects.org/index.php/Work_Breakdown_Structure

https://www.runn.io/blog/bottom-up-estimating


Other:


https://www.projectmanagement.com/contentPages/wiki.cfm?ID=510124&thisPageURL=/wikis/510124/Top-Down---Bottom-Up-Estimates-Comparison-#_=_

Iron Law of Mega Projects Bent Flyvbjerg https://towardsdatascience.com/the-iron-law-of-megaprojects-18b886590f0b

References

  1. ↑ 1.0 1.1 1.2 1.3 Project Management: "Managing Successful Projects with PRINCE2" 6th Edition (2017) Chapter 9.4 pp 116-118,”
  2. ↑ FreshBooks - Top-Down Estimating: Definition, Methods, Pros & Cons,” Available online: https://www.freshbooks.com/en-za/hub/estimates/top-down-estimating
  3. ↑ 3.0 3.1 3.2 3.3 (PMBOK Guide) Sebastian - Estimating Activity Durations: Definition, Methods, Practical Uses,” Available online: https://project-management.info/estimating-activity-durations/#6-expert-judgement
  4. ↑ 4.0 4.1 Project Management: A guide to the Project Management Body of Knowledge (PMBOK guide), 7th Edition (2021) Chapter 4.4.2 Estimating pp 178-
  5. ↑ B. Flyvbjerg - Estimating Cost of a Project: Techniques and Examples,” Available online: https://towardsdatascience.com/the-iron-law-of-megaprojects-18b886590f0b

Cite error: <ref> tag with name "two" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "four" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "four" defined in <references> is not used in prior text.

Retrieved from "http://wiki.doing-projects.org/index.php?title=Estimation_Techniques&oldid=140676"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox