Skip to main content
Back to course
Build the first estimate

Locate uncertainty in the work

5 min · Build the first estimate

Break the option into independently discussable slices. For each one, record its outcome link, included work, assumptions, dependencies and evidence basis.

Classify uncertainty only after naming its driver. Relevant comparison data and no material unresolved dependency may support a lower-uncertainty label. Novel technology, external systems or unanswered design questions may make uncertainty material. If evidence cannot support a useful range, investigate first.

Avoid automatic percentage uplifts unless your organisation has calibrated them against its own outcomes.

Reading

core

Uncertainty belongs to a driver

For each work slice, ask what assumption, dependency or novelty could materially change the implementation. Record a learning action next to every material driver. If no feasible action can make the estimate decision-useful, reduce the option or stop and investigate.

This lightweight practice borrows transparency principles from GAO guidance; it is not a substitute for quantitative risk and uncertainty analysis.

Worked example and transfer practice

All examples below are fictional teaching material. Use synthetic notes; no workplace or personal data is required or uploaded.

Locate the uncertainty before adding money. For the fictional reconciliation option, one export format is documented, while the second may omit transaction identifiers. Name the second connector as a material uncertainty. A five-day synthetic extraction test will check whether records can be matched reliably. Stop or reduce the option if the identifier is unavailable. A uniform buffer would not reveal which evidence could change the estimate.

Try before reading the guide: Record one uncertain work slice, its assumption, an evidence action, an owner and an end condition. Explain the decision if the action cannot resolve the unknown.

Practice review guide

The action is bounded and tests the named driver. A generic request to ‘research more’ has no stopping rule. A range may remain appropriate when useful evidence cannot support one precise value.

Knowledge check

core

Practice · formative check

Check the uncertainty treatment

Choose the response that makes uncertainty actionable.

Concepts: uncertainty driver, learning action

1. Vendor documentation for a critical legacy API is incomplete. What should the estimate record?

There is no attempt limit or pass/fail state. Completing the check only enables the lesson's separate explicit completion control; it never records completion or certificate eligibility itself.

Activity ready. Attempts are unlimited. Completing this practice activity enables the lesson's separate, explicit completion control.

Equivalent non-interactive path

Answer and feedback guide

Vendor documentation for a critical legacy API is incomplete. What should the estimate record?

  • Name the API as a driver, run a bounded extraction test and re-estimate at that checkpoint (best answer): Correct. The uncertainty is local and tied to evidence.
  • Add the same contingency percentage to every work slice: This obscures which evidence could change the range.
  • Exclude the dependency from the estimate discussion: A material dependency should be visible to the decision-maker.

Sign in to save progress across devices.Sign in

Course outlineLesson 2 of 3