Sprint - Storypoint Estimation

Story point model guidelines for estimation

We follow power of 2 pointing model:

Story point 1, 2, 4 - probably prod/QA bugs

Story point 8, 16, 32, 64, 128, 256 can be considered as sizes XS, S, M, L, XL, XXL respectively in terms of complexity.

Reference for storypoint calculation

Any stories that are bigger than this should goes as epic

Breaking down of stories -> Tasks :

Example: Talon.one Story - 128 pts

1. Exploration, R&D - also assign it to the respective developer

2. Reading Docs

3. API development

4. Brainstroming

5. Testing

Always try to breakdown the tasks into small pieces as much as possible

In Sprint planning,

* Pick tasks from backlog to sprint backlog - align it with roadmap.

* Discuss the plan of doing , clarify the requirement.

* Refine the estimation, breakdown the tasks and assign it to the team

* Plan the sprint goal.