Revision as of 21:32, 9 April 2023

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. 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. 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. 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.

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 does 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 and 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. 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

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. 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. 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 x 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

Conclusion

Annotated bibliography

H. Kwon and C. W. Kang, “Improving Project Budget Estimation Accuracy and Precision by Analyzing Reserves for Both Identified and Unidentified Risks,” Project Management Journal, vol. 50, no. 1, pp. 86–100. This article provides the reader important information about how to estimate the budget accurately, when is the best time to calculate the budget and which cost estimation method is the optimal method for all types of project.

D. A. N. Gregory K. Mislick, Cost Estimation: Methods and Tools. This E-book provides the overview of all cost estimation methods and tools to estimate the cost for all types of project. It has detailed description of estimated tools which can estimate cost of enterprise projects with maximum precision.

R. T. Hughes, “Expert judgement as an estimating method,” Information and Software Technology, vol. 38, no. 2, pp. 67–75, Jan. 1996. This article gives the reader an important information about expert judgment-based estimates of projects specifically in information technology and software domain

C. E. Clark, “Letter to the Editor—The PERT Model for the Distribution of an Activity Time,” Operations Research, vol. 10, no. 3, pp. 405–406, Jun. 1962. This article guides the reader how to use the PERT distribution, estimate the activity duration and cost accurately and how it is efficient method as compared to other estimation methods.

References

Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.