task-estimationlisted

# Task Estimation ## When to use this skill - **Sprint Planning**: Decide what work to include in the sprint - **Roadmap creation**: Build long-term plans - **Resource planning**: Estimate team size and schedule ## Instructions ### Step 1: Story Points (relative estimation) **Fibonacci sequence**: 1, 2, 3, 5, 8, 13, 21 ```markdown ## Story Point guidelines ### 1 Point (Very Small) - Example: text change, constant value update - Time: 1-2 hours - Complexity: very low - Risk: none ### 2 Points (Small) - Example: simple bug fix, add logging - Time: 2-4 hours - Complexity: low - Risk: low ### 3 Points (Medium) - Example: simple CRUD API endpoint - Time: 4-8 hours - Complexity: medium - Risk: low ### 5 Points (Medium-Large) - Example: complex form implementation, auth middleware - Time: 1-2 days - Complexity: medium - Risk: medium ### 8 Points (Large) - Example: new feature (frontend + backend) - Time: 2-3 days - Complexity: high - Risk: medium ### 13 Points (Very Large) - Example: payment system integration - Time: 1 week - Complexity: very high - Risk: high - **Recommended**: Split into smaller tasks ### 21+ Points (Epic) - **Required**: Must be split into smaller stories ``` ### Step 2: Planning Poker **Process**: 1. Product Owner explains the story 2. Team asks questions 3. Everyone picks a card (1, 2, 3, 5, 8, 13) 4. Reveal simultaneously 5. Explain highest/lowest scores 6. Re-vote 7. Reach consensus **Example**: ``` Story: "Users can upload a profile photo"