Estimate

• S (Small): < 2 hours — single file change, straightforward logic
• M (Medium): 2-6 hours — multiple files, some complexity, needs tests
• L (Large): 1-2 days — cross-module changes, new patterns, significant testing
• XL (Extra Large): 3-5 days — architectural changes, new infrastructure, coordination needed

Step 3: Risk Assessment

Identify risks that could expand the estimate:

Common risks:

• Unclear requirements → ask clarifying questions first
• Legacy code with no tests → add time for writing tests
• External dependencies → add time for integration
• Database migrations → add time for rollback planning
• API changes → add time for consumer coordination

Step 4: Dependencies

List any blockers or prerequisites:

• Other issues that must be completed first
• External services or APIs that must be available
• Team members who need to be consulted
• Infrastructure or access requirements

Step 5: Total Estimate

Rules

• Be honest — over-optimistic estimates hurt more than conservative ones
• Include testing and review time in estimates
• Flag any assumptions you're making
• If the task is too vague to estimate, say so and list the questions that need answers