What is planning poker and how it helps teams estimate

Planning poker is an estimation technique in which each team member secretly picks a card with the effort they believe a story will take. Everyone reveals at the same time. If the numbers match, the estimate is done. If they don't, the people who voted highest and lowest explain their reasoning and the team votes again.

The secret vote is the whole point. Nobody gets pulled toward the most senior person's number, and different understandings of the work surface immediately, before they turn into rework mid-sprint.

Where it came from

James Grenning described the technique in the early 2000s, and Mike Cohn's book Agile Estimating and Planning made it popular. It is a lean version of the Wideband Delphi method, created in the 1970s to estimate projects with input from several experts without letting them influence each other.

With remote and hybrid teams, the physical deck became an online room: a link, cards on the screen and a synchronized reveal for everyone.

Why it works

• It avoids anchoring. When someone says "that's a 3" before the others, the rest tend to agree. With a hidden vote, every estimate is independent.
• It surfaces what nobody said. A 2 and a 13 on the same story almost always mean two people pictured different work. The conversation after the reveal fixes that.
• It shares ownership. The people who build it estimate it. The number stops being one person's promise and becomes a team agreement.
• It is fast. With well-written stories, a round takes a few minutes.

Relative estimates, not hours

In planning poker the team compares stories with each other. The question isn't "how many hours will this take?" but "is this bigger or smaller than that story we already did?". That is why card values grow in jumps: the difference between 1 and 2 is easy to feel, the difference between 20 and 21 isn't.

The most common decks are:

Deck	Values	When to use
Fibonacci	0, 1, 2, 3, 5, 8, 13, 21…	The default for most teams
Modified Fibonacci	0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100	Backlogs with both tiny and huge items
T-shirt sizes	XS, S, M, L, XL	Early estimates, roadmaps, teams that don't use points
Powers of 2	1, 2, 4, 8, 16, 32	Teams that prefer doubling at each level

Besides numbers, most decks include a ? card for "I can't estimate this" and a break card for when the team needs a pause.

Who takes part

• The development team votes: front end, back end, QA, design, data. Whoever does the work estimates it.
• The product owner presents the story and answers questions, but usually doesn't vote.
• The facilitator, often the Scrum Master, runs the rounds and keeps time.
• Observers, such as managers, can watch without being counted as voters.

When the team doesn't agree

Not reaching a number in the first round is normal and healthy: that conversation is exactly what the method is designed to trigger. A few practical rules help:

1. Ask the people at the extremes to explain in up to a minute each.
2. Vote again. The second round usually converges.
3. If the gap is still large, the story probably needs to be split or refined first.
4. If the gap is small, like 5 and 8, pick the higher value or use the suggestion and move on.

Online planning poker with StoryPoints

With StoryPoints you create a room in one click, send the link to your team and everyone votes from a laptop or a phone, with no sign-up. When cards are revealed, the room shows the vote distribution, the team's agreement and a suggested estimate, and you can export the results as CSV at the end of the meeting.