Estimation: An Approximation That Narrows with Information, Not Certainty

Every project plan rests on numbers about things that have not happened yet: how long this activity takes, and what it costs. The trouble is that those numbers appear in schedules with the same confidence as facts, so everyone treats them as commitments rather than estimates. Performance is then measured against them, and the team is blamed for deviating from what was a structured guess from the start. Estimating is the discipline of handling that approximation: choosing the technique that matches the information available, expressing uncertainty instead of hiding it, and re-estimating rather than clinging to an old number.

Definition and Foundation

In the Eighth Edition an estimate is a quantitative assessment of a variable's likely amount or outcome, such as project effort or duration. Two halves of that definition are routinely conflated:

• Effort — the number of labor units required to complete a schedule activity or WBS component, often expressed in hours, days, or weeks.
• Duration — the number of work periods needed to complete individual activities with the estimated resources.

An activity with 40 hours of effort may have a duration of one week if one person works on it full time, or two days if three people do. The two numbers are different, and neither is derived from the other without knowing the assigned resources, their productivity, and their availability.

Estimates are progressively elaborated: the process considers the quality and availability of the input data, so as more detailed and precise data become available about engineering and design work, accuracy improves. An estimate is not an event that happens once in planning but a value refined as the unknown narrows. Factors that may influence duration estimates include constraints on duration, the effort involved, the type of resources, the experience of the team executing the activity, and the risk within it. The inputs come from the person or group most familiar with the nature of that specific work — not the manager and not the sponsor.

How It Works in Practice

Expert judgment and the Delphi technique

Expert judgment is judgment provided on the basis of expertise in an application area, discipline, or industry as appropriate for the activity being performed, and it may come from any group or person with specialized education, knowledge, skill, experience, or training. The Eighth Edition lists it first among the techniques for estimating effort and duration — but resting on one person exposes the estimate to the bias of the loudest opinion.

Which is where Delphi comes in: an estimating method in which subject matter experts go through multiple rounds of producing estimates individually, with a team discussion after each round, until consensus is achieved. It is one of the approaches using the diverge/converge pattern, engaging individual input and voting at the same moment in a way that minimizes groupthink.

Analogous estimating

A technique for estimating the duration, cost, or required resources for an activity or project using historical data from a similar activity or project. It takes parameters from a previous, similar project — duration, budget, size, weight, complexity — as the basis for estimating the same parameter for a future one. It is a gross value estimating approach, sometimes adjusted for known differences in complexity, and is frequently used when detailed information about the project is limited. It is generally less costly and less time-consuming than other techniques but can also be less accurate. It is most reliable under two conditions together: the previous activities must be similar in fact and not just in appearance, and the people preparing the estimate must have the needed expertise.

Parametric estimating

A technique in which an algorithm calculates cost or duration based on historical data and project parameters, using a statistical relationship between historical data and other variables — square footage in construction, for instance. Durations can be determined quantitatively by multiplying the quantity of work by the labor hours per unit. The guide's example: a resource installing 25 meters of cable per hour needs 40 hours for 1,000 meters. Its accuracy depends entirely on the quality of the historical data behind the formula.

Bottom-up estimating

A method of estimating duration, cost, or required resources by aggregating the estimates of the lower-level components of the work breakdown structure. When an activity's duration cannot be estimated with a reasonable degree of confidence, the work within it is decomposed into more detail, the detailed durations are estimated, and those estimates are aggregated into a total. It is the most accurate and the most time-consuming, and its precondition is that the work is already decomposed — it cannot be applied to scope that has not been broken down.

Multipoint estimating

A method of estimating cost or duration by applying an average or weighted average of three estimates: most likely tM, given the resources likely to be assigned, their productivity, realistic availability, and interruptions; optimistic tO, based on the best-case scenario; and pessimistic tP, based on the worst. Its purpose is to improve the accuracy of single-point estimates by accounting for estimation uncertainty and risk, producing an approximate range rather than a single figure. The commonly used formula given in the Eighth Edition is the triangular distribution tE = (tO + tM + tP) / 3, used when historical data is insufficient or when relying on judgmental data.

On the Exam

The 2026 ECO spreads estimating across two tasks in Domain II, Process: Task 1, develop an integrated project management plan and plan delivery, with the enabler "estimate work effort and resource requirements"; and Task 8, plan and manage schedule, with two enablers — "estimate project tasks (milestones, dependencies, story points)" and "utilize benchmarks and historical data."

The dominant pattern is a scenario describing how much information is available and asking which technique fits. The key is the information on hand, not the desire for precision:

• Data from a similar past project and little time → analogous.
• Reliable historical data linking a quantity to a rate → parametric.
• A detailed WBS and a need for maximum accuracy → bottom-up.
• High uncertainty on one particular activity → multipoint.

Three things do the deceiving. An option proposing bottom-up at a stage where scope has not been decomposed, which looks most accurate but is not applicable at all. An option proposing analogous on the basis of a project that resembles the current one in appearance rather than in fact. And a stem that mixes effort with duration, pushing you toward a calculation that cannot hold.

Detailed Mistakes

Presenting an estimate as a single number with no range

A single figure hides uncertainty rather than removing it. The guide is explicit that the accuracy of single-point estimates can be improved by considering estimation uncertainty and risk, and that multipoint estimates help define an approximate range. Offering "six weeks" instead of "five to eight weeks" buys apparent clarity at the cost of the one piece of information that actually helps a decision: the spread.

Conflating effort with duration

Effort is labor units; duration is work periods. Getting from one to the other runs through the assigned resources, their productivity, and their availability. Summing the effort of every activity and calling the result a project duration ignores parallelism and dependencies at once, producing a number tied to neither the schedule nor the budget.

Treating an estimate as a contractual commitment

An estimate is a value refined through progressive elaboration as better data arrives. Freezing it at the outset and then measuring performance against it for months converts a planning instrument into a blaming instrument. Revisiting an estimate is not an admission of failure; it is the correct use of the tool.

Where It Does Not Apply

Absolute estimating in hours presumes an ability to predict precise durations, and that weakens in fast-changing environments. This is why the guide notes that many agile teams use story points instead: story points reflect relative effort or complexity rather than absolute time, based on the understanding that teams are typically better at comparing work items than at predicting precise durations. The approach simplifies planning while preserving accuracy, since estimating hours can be more time-consuming and less reliable in dynamic environments. The question, then, is not which technique is most accurate in the abstract, but which one matches how stable the information is on this project.