Analogous Estimating
How Analogous Estimating Works
Your team just won a new project and the sponsor wants a budget by Friday. The scope is a two page summary. You do, however, have detailed records from a similar project you delivered last year.
That previous project becomes your baseline. Adjust for the known differences, and you have an estimate that is defensible without weeks of work breakdown.
The technique works from the top down. Start with actual duration or cost data from a completed project that shares comparable scope, complexity, and conditions.
Then apply expert judgment to adjust for what has changed. If the last website redesign took 14 weeks and the current one adds an e commerce module, the adjusted estimate might land at 17 weeks.
The adjustment is where the skill lives, because identical projects do not exist. Every estimate depends on the estimator’s ability to size the gap between past and present.
Two inputs drive the method: historical records from completed work and judgment to assess similarity. Without reliable records, there is no valid reference point. Without experienced judgment, the adjustments are guesses.
Commonly Confused With
| Term | Key Difference |
|---|---|
| Parametric Estimating → | Analogous estimating uses a whole project comparison ("the last one took X"). Parametric estimating uses a unit rate applied to a quantity ("$Y per square foot x Z square feet"). Parametric is more precise when reliable unit rates exist. |
| Bottom Up Estimating | Bottom up estimating builds the total from detailed estimates of every work package. Analogous estimating works from the top down using a past project as a proxy. Bottom up is more accurate but requires detailed scope and far more effort. |
| Expert Judgment | Expert judgment is one input to analogous estimating (the adjustment for differences). Analogous estimating also requires actual historical data. Pure expert judgment without historical data is opinion based estimating, not analogous estimating. |
When to Use Analogous Estimating
Use this technique early in the project lifecycle when only high level scope exists and there is not enough detail for parametric or bottom up methods. PMI’s PMBOK Guide classifies it as a rough order of magnitude approach, typically producing estimates accurate within minus 25% to plus 75% of the final outcome.
It fits best when the organization maintains records of completed projects, when the new project genuinely resembles a past one, and when an experienced estimator can quantify the differences.
Construction firms estimating a new office buildout from a recent one, IT departments sizing a migration from a previous rollout, and agencies quoting a campaign from a similar client engagement all use this pattern daily.
When Analogous Estimating Falls Short
The technique breaks down in three situations. First, when no comparable project exists. Novel technology, first entry into a new market, or an entirely new product category leaves you without a valid reference. The estimate becomes a guess dressed as data.
Second, when the gap between past and present is too wide for adjustment. A 10 person SaaS build is not a useful proxy for a 200 person ERP implementation, even if both qualify as “software projects.”
Third, when the stakes demand precision. For firm fixed price contracts, regulatory submissions, or resource commitment decisions, bottom up estimating delivers the accuracy those contexts require.
Research published in the International Journal of Project Management found that analogous estimates averaged roughly 30% deviation from actual outcomes, compared to about 10% for detailed bottom up methods when scope was well defined. The speed advantage only pays off when the accuracy tolerance is wide enough to absorb it.
Improving Accuracy
Accuracy improves with better inputs. Document the actual cost and duration of every project at close out, not just the original estimate. Categorize completed projects by type, complexity, team size, and technology so future estimators can find the closest match quickly.
When adjusting, be specific about what differs and assign a value to each difference. “The current project has a tighter compliance requirement” is vague. “The compliance review adds approximately 80 hours based on regulatory scope” is an adjustment the team can evaluate. Written adjustment logs also make the estimate defensible in stakeholder reviews and auditable for post project learning.
Common Questions About Analogous Estimating
What inputs do you need for an analogous estimate?
Two things: actual cost or duration data from a completed project with similar characteristics, and expert judgment to assess where the current project differs and quantify those adjustments. Without historical records, the method has no valid starting point.
How accurate is analogous estimating?
Rough order of magnitude accuracy, typically within minus 25% to plus 75% of the actual outcome. Accuracy improves significantly when the reference project closely matches the current one in scope, technology, team size, and organizational context. For budgeting or contract pricing, switch to bottom up or parametric methods.
When should I use analogous instead of parametric estimating?
Use analogous when you have a comparable completed project but lack reliable unit rate data for parametric calculations. Parametric estimating needs a quantifiable cost driver like dollars per square foot or hours per user story. If you have that data, parametric is more precise. If not, analogous gives you a faster starting point from a real project baseline.
What makes a good reference project for analogous estimating?
Similar scope, complexity, technology stack, team size, and organizational context. The more dimensions that align, the smaller the adjustment and the more reliable the result. Document which project you used and what adjustments you applied so the estimate stays traceable.