How to play planning poker with your team
Planning poker turns “how big is this?” into a conversation. Your team estimates a piece of work independently, reveals the cards together, and compares assumptions before agreeing on a size. Also called Scrum poker, it works for teams sharing a table or joining online.
Prepare the story and the scale
Pick one backlog item and explain the outcome it should deliver. Talk through acceptance criteria, dependencies, and what “done” includes. Include testing and review in the estimate if they are part of your team’s definition of done. Invite the people who will do the work; a facilitator can keep the discussion moving.
Story points compare work, rather than count hours
Story points express relative size. Teams often consider effort, complexity, and uncertainty together. Choose a familiar completed item as a reference: if a small, well-understood change is a 2, how does this story compare? Keep that reference consistent within your team. A 5 on one team does not have to equal a 5 on another, and points should not be used to compare individual productivity.
Run a round in Pointless Poker
- Open Pointless Poker and choose “Create a room.” Pick your name and character. No signup is required.
- Share the invitation link with your teammates. They can join from a desktop, tablet, or phone. Discuss the story using your usual conversation or meeting tool.
- Have the host choose a deck. Each player picks a card privately; other players can see that a vote was cast, but not its value.
- Once everyone is ready, the host reveals the cards. Compare the estimates and ask what led people to choose different values.
- Agree on an estimate, or have the host start a new round to vote again after clarifying the work. Record the agreed estimate in your backlog tool, then move on to the next story.
The shared reveal helps each person form an estimate before seeing someone else’s number. The aim is a shared understanding of the work; matching cards are useful, but the discussion matters more.
A worked story-point example
Imagine a story to let users reset a password by email. Your team’s reference story is a 3-point profile form change. The first votes for the reset flow are 3, 5, and 8.
The player voting 3 expects to reuse an existing email service. The player voting 8 is accounting for expired tokens, rate limiting, and testing the recovery flow. Neither number tells the whole story: the team was estimating different scopes.
Clarify which protections already exist and add the missing acceptance criteria. Vote again with the same understanding. The team might settle on 5, or split off a larger dependency first. This is an illustration, not a recommended point value for password reset work on every project.
Choose an estimation deck
Fibonacci planning poker uses widening gaps between values to avoid pretending that large, uncertain work can be measured precisely. Pointless Poker supports these options:
- Fibonacci: 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89.
- Modified Fibonacci: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100.
- T-shirt sizes: XS through XXL for a broad relative scale.
- Linear: 1 through 10, with equal steps.
- Powers of two: 1, 2, 4, 8, 16, 32, 64.
- Custom: 2–16 values that fit your team’s shared scale.
The built-in decks also include “?” for uncertainty and a coffee card for a break. Pick a scale the team understands and keep it consistent across comparable stories. Changing the labels does not remove the need to agree on what they mean.
Handle disagreement and uncertainty
Start by inviting the lowest and highest estimators to explain their assumptions. Ask about dependencies, unfamiliar technology, testing, and scope. Avoid simply averaging the votes: an average can hide a disagreement about what needs to be built.
If someone chooses “?”, find out what information is missing. A short investigation or a smaller story may be more useful than another vote. If several rounds produce no new information, note the uncertainty and agree on a next step instead of forcing identical estimates.
Planning poker is one way to support agile estimation, not a requirement for Scrum. Use it where conversation improves your planning, and revisit your reference stories as the team learns.
Your team. A few cards. A clearer plan.
Try free planning poker online with your next story. Create a room, invite your teammates, and reveal your estimates together.
Start planning poker