Free Planning Poker by TeamRetro

Planning Poker is an agile estimation technique where team members assign story points to user stories based on their complexity, effort, and uncertainty—helping teams plan sprints more accurately. It promotes team consensus and surfaces differing perspectives early.

Planning Poker is a simple, team-based way to estimate work by combining shared understanding and quick consensus.

1. Pick a backlog item (user story/task) to estimate.
2. Review the details: goal, scope, and acceptance criteria. Ask clarifying questions.
3. Choose your estimate privately using the agreed scale (commonly Fibonacci: 1, 2, 3, 5, 8, 13…).
4. Reveal estimates at the same time so no one influences others.
5. Discuss differences if estimates vary—especially the highest and lowest—to uncover risks, assumptions, or missing details.
6. Refine the item if needed (clarify requirements, note assumptions, or split the work).
7. Re-estimate and repeat until the team reaches a reasonable agreement.
8. Move to the next item and keep going until you’ve estimated what you need.

Typically the Scrum Master facilitates to keep time and ensure everyone participates. The Product Owner presents stories and answers questions but shouldn’t vote. Some teams rotate facilitation to build shared ownership.

Use an online Planning Poker tool where team members join a shared room, vote secretly, and reveal estimates together. Screen sharing, video calls, and chat help replicate the collaborative discussion that happens in person.

Aim for 1–2 hours max. Estimate 5–10 stories per session depending on complexity. If discussions run long, it often means stories need more refinement before estimation. Take breaks to maintain focus and energy.

Wide variance signals misunderstanding or hidden complexity. Have the highest and lowest voters explain their reasoning—often they’ve spotted risks or assumptions others missed. Discuss, clarify, and re-vote until the team aligns.

If estimates vary, the team discusses the reasoning behind their points. This often uncovers misunderstandings or missing details in the user story, leading to better alignment.

To ensure a successful planning and estimation session with your team:

Story points are an abstract measure of effort, risk, and complexity—not time. In Planning Poker, team members vote using story point values to estimate how challenging a user story is relative to other stories the team has completed.

Yes! It’s ideal to use during either session. Start by discussing the story, confirming acceptance criteria, and then begin estimation.

No account is required for instant use and allows you to reuse the same room number for future planning and estimation sessions.

Our users trust us to keep their data secure and confidential. We take privacy and security seriously and work constantly to ensure that trust is well-founded. You can read more about our security policies at help.teamretro.com/article/463-planning-poker-privacy-security.