Description
Outside view calibration: reference class definition, distribution extraction, inside-to-outside estimate formula.
Inside view forecasting — estimating based on the specifics of your project — is systematically optimistic. Outside view asks: how did similar projects actually perform? Without this calibration, estimates are 2-3× too low on time and 1.5-2× too low on budget. STEP 1 — REFERENCE CLASS DEFINITION Identify the widest set of projects that share the essential features of yours. The reference class must be broad enough to have statistical data, but narrow enough to be relevant. For a software migration project: reference class = 'enterprise platform migrations (ERP transition, cloud migration, monolith-to-microservices).' Collect 10+ data points from internal post-mortems, industry reports, academic studies, or direct peers. STEP 2 — DISTRIBUTION EXTRACTION Plot the reference class outcomes. Compute: - Median time: the 50th percentile. If half of migrations took longer than 18 months, your migration will probably take longer than 18 months. - Lower quartile: the optimistic 25% — what went right for those? - Upper quartile: the pessimistic 75% — what went wrong? - Range factor: max/min ratio. Factor >10 means the class is too broad. Narrow it. STEP 3 — YOUR INSIDE ESTIMATE Write down your team's inside view estimate (time, budget, scope). This is the number you would give stakeholders today. Be honest — this is the number you protect against. STEP 4 — CALIBRATION FORMULA Calibrated estimate = your inside estimate × (reference class median / your team's typical accuracy factor). If the reference class median is 14 months and your team over-delivers by 20% on average, calibrated = inside × (14 / (inside × 0.8)) — adjusting the median to your team's actual delivery profile. STEP 5 — THREE SCENARIOS - BEST CASE (lower quartile): What would have to go perfectly? Usually means zero dependencies, perfect requirements, no personnel changes. - MEDIAN CASE (reference class median): The most likely outcome. If you present only 'realistic' and 'optimistic', the team will pick optimistic. Force median visibility. - WORST CASE (upper quartile): What would have to go wrong? Usually means requirements change, key person leaves, integration with legacy system proves deeper than expected. STEP 6 — DECISION WORKSHOP Given the outside view, does the project still make sense? If the median estimate exceeds the maximum acceptable cost, the project should not proceed without scope reduction. This is the point where inside view bias is most dangerous — you will rationalize. The outside view is the corrective. OUTPUT: Reference class data + distribution, inside estimate, calibrated estimate, three-scenario table, go/no-go decision with rationale.
No comments yet. Be the first!