HKSM

A technique that uses more than one estimate—commonly optimistic, most likely, and pessimistic—to produce an expected cost and quantify uncertainty. It enables range-based estimates and supports setting appropriate contingencies.

Key Points

• Uses multiple estimate points per item to reflect uncertainty instead of a single number.
• Common formulas include triangular average (O + M + P) / 3 and beta-weighted average (O + 4M + P) / 6.
• Calculates a mean (expected cost) and variability (e.g., standard deviation = (P − O) / 6).
• Applied at activity or work package level and then summed to higher levels for a total estimate.
• Supports contingency sizing and confidence levels, and complements risk and reserve analysis.
• Relies on expert judgment, historical data, and clear assumptions to set realistic ranges.

Purpose of Analysis

To reflect real-world uncertainty in cost estimates and avoid false precision. It helps set credible ranges, quantify risk exposure, and align funding with the organization’s risk appetite. It also improves stakeholder confidence by showing the logic behind contingencies.

Method Steps

• Select scope items to estimate (activities or work packages) and define what is included.
• Identify key cost drivers and gather reference data and expert inputs.
• Elicit three points per item: Optimistic (O), Most Likely (M), and Pessimistic (P), with explicit assumptions.
• Choose a formula: triangular average for simplicity, or beta-weighted average when the most likely value deserves more weight.
• Compute expected cost and standard deviation for each item.
• Determine target confidence (e.g., 80% or 90%) and derive contingency from variability.
• Document basis of estimate, assumptions, exclusions, and data sources.
• Aggregate results to control accounts and the project total; check for correlations between items.
• Review with SMEs, refine ranges if needed, and update the risk register and reserves.

Inputs Needed

• Scope and WBS details with clear definitions of work packages.
• Resource rates, vendor quotes, bills of materials, and pricing catalogs.
• Historical cost data, benchmarks, and lessons learned from similar work.
• Risk register entries that influence cost uncertainty and ranges.
• Organizational estimating policies, templates, and cost assumptions.
• Schedule assumptions and constraints that affect cost (e.g., overtime, rush fees).

Outputs Produced

• Expected cost per item and aggregated expected project cost.
• Cost ranges and confidence intervals for items and the overall estimate.
• Standard deviation or variance by item to inform contingency sizing.
• Contingency recommendations aligned to a target confidence level.
• Basis of estimate documenting methods, assumptions, and data sources.
• Updates to the risk register and cost-related risk responses.

Interpretation Tips

• Use beta-weighted averaging when the most likely value is well supported; use triangular when data are limited.
• A wide (P − O) range signals higher risk; consider mitigation or more detailed estimating.
• Do not assume items are independent; account for correlation to avoid underestimating total variability.
• Ensure all values use the same price base and include applicable taxes, freight, and overheads.
• Report ranges and confidence levels clearly; avoid rounding too early.
• Visualize results with histograms or S-curves to communicate uncertainty.

Example

Work package: Purchase and configure data migration tools. Expert inputs: O = $18,000, M = $22,000, P = $35,000.

• Beta-weighted expected cost = (18,000 + 4×22,000 + 35,000) / 6 = $23,500.
• Standard deviation ≈ (P − O) / 6 = (35,000 − 18,000) / 6 ≈ $2,833.
• For an 80% confidence target, contingency ≈ 0.84 × SD ≈ 0.84 × 2,833 ≈ $2,380.
• Budget recommendation for this item ≈ $23,500 + $2,380 ≈ $25,880, with a documented range.

Pitfalls

• Setting O and P too close to M, understating uncertainty.
• Copying the same ranges across different items without considering unique drivers.
• Ignoring correlations or systemic risks, leading to optimistic rollups.
• Double-counting risk by padding estimates and also adding full risk reserves.
• Excluding fees, taxes, or currency effects, creating hidden gaps.
• Poor documentation of assumptions, making the estimate hard to defend.

PMP Example Question

While estimating a high-uncertainty work package, the sponsor asks for both an expected cost and a clear basis for contingency. What should the project manager do next?

1. Ask the lead SME for a single-point analogous estimate and add a management reserve.
2. Apply three-point estimating to derive an expected cost and standard deviation, then size contingency to a target confidence level.
3. Request firm fixed-price quotes and remove contingency to avoid padding.
4. Add a flat 20% buffer to the current estimate to cover unknowns.

Correct Answer: B — Apply three-point estimating to derive an expected cost and standard deviation, then size contingency to a target confidence level.

Explanation: Multipoint estimating provides a mean and variability, which supports risk-informed contingencies. Single-point guesses or arbitrary padding are not defensible for high-uncertainty items.