HKSM

Bottom-up estimating determines effort, duration, or cost by estimating detailed activities or work packages and then aggregating the results to higher levels. It is thorough and often more accurate, but takes more time and relies on a well-defined scope.

Key Points

• Estimates are created at the activity or work package level and rolled up to summaries and totals.
• Requires a complete WBS, clear scope, and defined resources to be effective.
• Often provides higher accuracy than top-down methods but takes more effort and time to develop.
• Produces a basis of estimates that documents methods, data sources, assumptions, and ranges.
• Can incorporate three-point estimates, vendor quotes, and risk-based reserves.
• Useful for validating analogous or parametric estimates and setting realistic baselines.

When to Use

• When the WBS and activity definitions are complete and detailed.
• For complex, high-risk, or high-visibility work that needs defensible estimates.
• When contracts or governance require a documented basis of estimates.
• To develop final cost and schedule baselines after initial top-down sizing.
• When prior analogous data is weak or not directly comparable.

How to Estimate

• Decompose deliverables into work packages and activities that are small enough to estimate credibly.
• Identify required resources, quantities, calendars, and productivity rates for each activity.
• Select estimating methods (single-point, three-point, vendor quote, parametric at micro-level) as appropriate.
• Calculate effort and duration per activity, then convert to cost using labor rates and unit prices.
• Document assumptions, constraints, data sources, and estimate ranges for each item.
• Aggregate estimates to work packages, control accounts, and the total project, adding risk-based contingency reserves.
• Review with the team and stakeholders, reconcile gaps, and update the basis of estimates.

Inputs Needed

• WBS and WBS dictionary with clear scope descriptions.
• Activity list and attributes, including dependencies and leads/lags.
• Resource requirements, resource calendars, and availability.
• Labor rates, unit costs, and standard cost elements.
• Historical data, benchmarks, and lessons learned.
• Risk register and results from early risk analysis.
• Vendor quotes, bills of materials, and procurement data.
• Organizational templates, estimating guidelines, and tools.

Outputs Produced

• Activity-level duration and cost estimates with ranges.
• Basis of estimates detailing methods, assumptions, and data sources.
• Consolidated work package and project totals with contingency reserves.
• Confirmed resource requirements and planned resource usage.
• Updates to the assumptions log, risk register, and estimate documentation.

Assumptions

• Scope is sufficiently decomposed and stable during estimating.
• Resource productivity and rates reflect realistic current conditions.
• Vendor quotes and unit prices remain valid for the planned period.
• Risks are identified and reserves are aligned to quantified exposure.
• No double-counting occurs when aggregating estimates and reserves.

Example

A team estimates a brochure project by itemizing activities: write content (16 hours), design layout (24 hours), edit (8 hours), and printing setup (fixed cost of 500). Labor rate is 50 per hour.

• Labor cost: (16 + 24 + 8) × 50 = 2,400.
• Printing setup: 500.
• Subtotal: 2,900; add 10% contingency for identified risks = 290.
• Total estimated cost: 3,190; basis of estimates captures sources, rates, and assumptions.

Pitfalls

• Missing activities due to incomplete decomposition, leading to underruns.
• Optimism bias from subject-matter experts providing best-case numbers.
• Confusing effort with duration or ignoring resource calendars and constraints.
• Not documenting assumptions, making future revisions and audits difficult.
• Insufficient risk allowance or double-counting reserves when rolling up.
• Failure to validate estimates against actuals or benchmarks.

PMP Example Question

A project has a well-defined WBS and detailed activity list. The sponsor asks for a highly reliable cost estimate. What should the project manager do next?

1. Use an analogous estimate based on a similar past project.
2. Apply bottom-up estimating and aggregate activity-level estimates.
3. Perform high-level parametric estimating using cost per unit.
4. Provide a rough order of magnitude estimate and refine later.

Correct Answer: B — Apply bottom-up estimating and aggregate activity-level estimates.

Explanation: With detailed scope and activities, bottom-up estimating provides more credible, defensible estimates than top-down approaches.