How Scrum Poker Works

What Is Scrum Poker?

Scrum Poker, often called Planning Poker, is a collaborative estimation method used by Scrum and Agile teams. Team members review a backlog item, discuss the work, and then vote independently using a shared estimation scale.

The purpose of Scrum Poker is not to predict exact hours with perfect accuracy. Its purpose is to help the team build a shared understanding of complexity, uncertainty, effort, and dependencies. This makes sprint planning more realistic and reduces the risk of hidden assumptions.

Because everyone votes independently before results are revealed, Scrum Poker reduces anchoring bias. Instead of following the loudest or most senior opinion, the team gets a more honest view of how difficult a task really is.

How the Scrum Poker Process Works

A typical Scrum Poker session follows a clear step-by-step workflow.

1. 1. Create a room
   Start by creating a room for your estimation session. A room gives your team a shared place to review tasks, vote, and discuss results in real time.
2. 2. Invite your team
   Send the room link to developers, designers, QA engineers, product managers, and anyone else involved in estimation. Remote teams can join instantly in the browser without complicated setup.
3. 3. Review the backlog item
   Before voting, the team reads the story, clarifies acceptance criteria, and asks questions. This step is important because unclear requirements usually lead to weak estimates.
4. 4. Choose a card independently
   Each participant selects a card based on their understanding of the work. Teams usually estimate with story points, often using the Fibonacci scale.
5. 5. Reveal votes together
   Votes are revealed at the same time. This helps prevent bias and makes differences in understanding immediately visible.
6. 6. Discuss large differences
   If estimates vary significantly, the team discusses assumptions, risks, technical unknowns, and complexity. These discussions are often the most valuable part of the session.
7. 7. Vote again if needed
   After discussion, the team can vote again. A second round usually leads to better alignment and a more confident estimate.
8. 8. Record the final estimate
   Once the team agrees, record the final story point value and move to the next item.

Why Teams Use Scrum Poker

Scrum Poker is popular because it improves both estimation quality and team alignment.

• It creates shared understanding before development starts.
• It reveals hidden complexity and missing details early.
• It reduces estimation bias by using independent voting.
• It gives the whole team a voice, not just the most senior person.
• It helps remote teams estimate in a structured and fast way.
• It supports better sprint planning and more realistic forecasting.

What a Typical Estimation Session Looks Like

A typical session begins with a facilitator or product owner presenting a backlog item. The team reviews the story, clarifies the goal, and makes sure the scope is understood.

Next, each team member selects an estimate privately. When everyone is ready, the votes are revealed together. If the numbers are close, the team may accept the result immediately.

If one person votes very low and another votes very high, that difference becomes a starting point for discussion. One person may see hidden complexity, while another may be making a different assumption about the implementation.

After a short discussion, the team votes again and records the final estimate. This process repeats for the next backlog item until the estimation session is complete.

Best Practices for Better Scrum Poker Sessions

• Keep backlog items small enough to compare effectively.
• Clarify requirements before asking the team to vote.
• Use one agreed estimation scale across the whole team.
• Encourage everyone to explain unusual estimates.
• Do not treat story points as exact hours.
• Use estimation to improve planning, not to measure individual performance.
• Re-estimate stories if scope changes significantly.

Frequently Asked Questions