Use when estimating time, effort, cost, or complexity for features, projects, refactors, and bug backlogs. Produces defensible estimates via triage, decomposition, risk handling, and confidence intervals, with clear assumptions and validation steps.
Create consistent, defensible estimates by:
Optimized for reviewing an existing project or backlog and producing a realistic delivery forecast.
Provide as much as possible; estimate quality depends on clarity.
Always confirm the estimate frame up front:
Unless provided, assume:
For each bug, capture:
Rule: If Repro=C or Clarity=C, include a discovery slice.
Estimate each item using this structure:
Use hours only for work expected to be under one day; otherwise use engineer-days.
Maintain an Unknowns Register:
Risk buffer guidance:
Produce:
Provide:
For each item:
A good estimate is: