Estimate Skill

When estimating work, follow this structured process. Good estimates are ranges, not single numbers. They account for complexity, risk, unknowns, and the reality that things always take longer than expected.

1. Understand What's Being Estimated

Before estimating, clarify the scope:

Gather Requirements

• What exactly needs to be built/changed? — Get specific, not vague
• What's the expected outcome? — How will we know it's done?
• What's explicitly out of scope? — Prevent scope creep
• Who is this for? — End users, internal team, API consumers?
• Are there design mocks? — UI work without mocks adds uncertainty
• Are there dependencies on other teams/services? — External dependencies add risk