Complete guide for successful Scrum Poker and story point estimation
Scrum Poker is an agile estimation technique where teams collaboratively assess the complexity of user stories in story points. This method is used in sprint planning and promotes team consensus, avoids anchoring effects, and ensures more accurate estimates.
The key feature: All team members estimate simultaneously and privately, so individual opinions don't prematurely influence the group. This leads to an honest assessment of effort and reveals different understandings early.
The Scrum Master or Product Owner creates a new room on the homepage. You receive a unique room code that you can share with your team.
Share the room code or direct link with all participants. Everyone can easily join without registration or login.
The Product Owner presents the user story to be estimated. Important: All team members should understand the acceptance criteria, definition of done, and technical details before estimating.
Each team member selects a card with story points privately. The Fibonacci scale (1, 2, 3, 5, 8, 13, 21, ...) is used because larger tasks are naturally harder to estimate.
Common Card Values:
Once all participants have chosen their card, the estimates are revealed simultaneously. This prevents the anchoring effect (influence from the first estimate).
With significantly different estimates, the team discusses. Especially those with the highest and lowest estimates explain their perspective. Then the team estimates again until consensus is reached.
After agreeing on an estimate, the round is reset and the next user story is estimated. Results are saved and can be viewed in the history.
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21...) is ideal for agile estimation because it reflects the increasing uncertainty with larger tasks:
Only those who will actually do the work should estimate. Scrum Masters and Product Owners facilitate but usually don't estimate.
Story points are relative sizes, not time estimates. Compare new stories with already estimated ones as reference.
Different estimates are valuable! They show different understanding or overlooked complexity.
Limit discussions to 2-5 minutes per story. If unclear: Mark story with "?" and clarify later.
Stories over 13 points should be broken into smaller, manageable pieces. This improves planability and velocity tracking.
Story points measure complexity, effort, and uncertainty – not time. A 5-point task may take different developers different amounts of time, but the relative complexity remains the same. This enables better velocity measurements across sprints.
Have the people with the most extreme estimates (highest & lowest) explain their perspective. This often reveals valuable insights about overlooked complexity or simplification opportunities. Then the team estimates again.
Yes! Our Scrum Poker tool supports custom cards. Some teams use T-shirt sizes (XS, S, M, L, XL) or their own scales. The Fibonacci scale is the proven standard though.
For a 2-week sprint, plan 2-4 hours. Experienced teams manage 10-20 user stories per hour. Important: Quality over speed – better to discuss thoroughly than estimate incorrectly.
Create a free room now and get started with your team!
Create Room Now →