Pointing Poker, Explained: Story Point Voting and Why Teams Also Call It Poker Planning

If you have heard a team say “let’s point this story” and also “time for poker planning” and also “open the planning poker room,” you have heard three names for one thing. Pointing poker, poker planning, planning poker, and scrum poker all describe the same activity: a team estimating work by voting with cards instead of arguing toward a number. The names differ by habit and region, not by method.

This post clears up the terminology and then walks through what a pointing session actually looks like — what you vote on, how the cards work, and how to run one without paying for a tool.

What pointing poker is

Pointing poker is a group estimation technique. The team takes one item of work — usually a user story from the backlog — and every member privately picks a card representing how much effort they think it will take. Everyone reveals at the same time. If the votes agree, the number is recorded and the team moves on. If they disagree, the people with the highest and lowest cards explain their reasoning, and the team votes again. A couple of rounds usually converges.

The point of voting privately and revealing together is to avoid anchoring. When the most senior person says “that’s a 5” out loud first, everyone else tends to drift toward 5. Simultaneous reveal keeps each estimate independent, which is where the honest disagreement — and the useful conversation — comes from.

Why it is called “pointing”

The “pointing” in pointing poker comes from story points. A story point is a unit of relative effort: instead of estimating a task in hours, the team estimates how big it is compared to other tasks. A story that is roughly twice the effort of a 3 gets a 5 or an 8, not “about six hours.” Assigning that number to a story is called pointing the story.

If story points are new to you, the agile story points guide explains how they work and why relative sizing tends to be more reliable than time estimates. Pointing poker is simply the voting ritual that produces those points.

How a pointing session works

A typical session runs like this:

1. The facilitator reads out one backlog item and answers quick clarifying questions.
2. Each team member privately selects a card with their estimate.
3. Everyone reveals at once.
4. If the cards match, record the number and move to the next item.
5. If they don’t, the highest and lowest voters explain briefly, then everyone votes again.

Most of the value is in step 5. A wide spread usually means the story is understood differently across the team — someone knows about an edge case, or someone assumed a simpler scope. Surfacing that before the work starts is the real reason the ritual exists. The number on the card matters less than the conversation it triggers. For a deeper look at the method itself, see what is the planning poker technique.

The deck

The standard deck uses a Fibonacci-style sequence — 1, 2, 3, 5, 8, 13, 21, and up — plus a few special cards (a question mark for “I don’t understand this yet,” and often a coffee cup for “let’s take a break”). The gaps widen on purpose: the bigger a story is, the less precise anyone can be about it, so there is no card between 13 and 21 to argue over. Some teams prefer T-shirt sizes (S, M, L, XL) for rougher, faster sizing. Both work; the deck is just a scale.

Running pointing poker for free

You do not need a paid tool to point stories. A few free options exist, and Scrum Poker Online — the tool we build — is one of them. A room is created from a shared link with no signup for participants, the default deck is Fibonacci, and registered users can switch to a custom scale like T-shirt sizes. It is free, funded by ads; the 40 USD/year Premium tier (per team, not per user) removes them and adds a session timer, attendance indicators, and automatic average and median. The honest limitation: there is no native Jira integration, so estimates are not written back to your backlog automatically — most teams keep the pointing tool open next to Jira and type the final number in.

If you want to compare the free options side by side, the online planning poker tools roundup covers several, including a couple with no paid tier at all.

Same game, different names

To settle the vocabulary once:

• Planning poker is the original term, coined by James Grenning and popularized by Mike Cohn.
• Pointing poker emphasizes the output — story points — and is common in teams that talk about “pointing” their backlog.
• Poker planning is the same words reordered; it usually means exactly planning poker.
• Scrum poker ties the practice to the Scrum framework, though nothing about the technique requires Scrum specifically.

Pick whichever name your team already uses. The practice underneath is identical: read a story, vote with cards, reveal together, discuss the spread, agree on a number. It takes ten seconds to explain and a few sessions to get comfortable with — and the tool you use to run it should stay out of the way of the conversation, which is where the actual estimating happens.