Principle
Let ranges narrow only when uncertainty is actually removed
Time passed is not evidence gained.
Before you use it
- Use when
- A project gets older, so forecasts become narrower by convention even though key unknowns remain.
Keep this limit in mind
- A wide range can be unhelpful if it never supports a decision; pair uncertainty with the next information that can reduce it.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
At each stage, identify which uncertainties were resolved and which remain. Narrow the range only when scope, design, dependencies or throughput have become materially better known. If new uncertainty appears, the honest range can widen again.
An example
After a prototype validates the interface and throughput, the range narrows; after an unexpected compliance review appears, it widens again.
Check your result
The width change has an evidence explanation.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingLet ranges narrow only when uncertainty is actually removed
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaAttach confidence to the evidence, not to your tone
Evidence and sources
IPA guidance notes that uncertainty and estimate range depend on the maturity and variability of input data, so estimates should evolve as design and evidence mature.
A later estimate can still be wrong; maturity narrows uncertainty only when real information has improved.
Cost Estimating Guidance · Estimate maturity and range
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.