Estimate a project when external access is uncertain

A precise date built on unknown credentials is false precision. Separate controllable engineering effort from external wait time.

Calculate three scenarios

The delivery lab uses authored work and access-delay assumptions.

from delivery_cases import estimate_case

result = estimate_case()
assert result["total_days"] == {"best": 10, "expected": 13, "worst": 20}
assert result["range"] == [10, 20]
assert result["commitment"] == "10 days after access, with calendar range 10-20 days"

Break work into discovery, access, build, test, review, deployment and handover. Identify dependencies with owner and needed-by date. Estimate effort relative to access, then add calendar scenarios. Build a local sandbox in parallel where it reduces risk, while preserving an integration step.

Update estimates when evidence changes and explain impact. Include contingency for uncertainty rather than hiding it inside every task. Do not count waiting as engineering effort, but do show its effect on delivery.

The FDE for Freshers course teaches honest estimates in discovery and scope.

Exercise

Estimate your capstone using three access scenarios and one vendor-review delay. State which assumption would move the range most.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Map stakeholders and decision owners in a small project.
• Continue with Explain a technical risk to a nontechnical client.

Reference: Agile Manifesto principles.