Planning Poker: The Complete Guide for Scrum Teams

What is planning poker?

Planning poker — sometimes called scrum poker — is a way for a scrum team to agree on how much effort a piece of work is likely to take, before that work is committed to a sprint. Instead of one person (usually the most senior engineer in the room) calling out a number that everyone else quietly defers to, every team member picks their own estimate privately and reveals it at the same time as everyone else.

The estimates are usually expressed in story points rather than hours or days — an abstract, relative measure of size and complexity rather than a time commitment. A story that's a 3 isn't promised to take three hours; it's roughly three times the effort of a story that's a 1, based on the team's own shared frame of reference.

Why teams use planning poker

The core problem planning poker solves is anchoring bias. In an open discussion, whoever speaks first sets a reference point, and everyone else's mental estimate drifts toward it whether they intend it to or not. A junior developer who privately thinks a story is an 8 will often say "yeah, 5 sounds right" once a senior teammate has already said 5 out loud.

Revealing every vote simultaneously breaks that chain. It also surfaces disagreement early and on purpose: if half the team estimates a story at 2 and the other half at 13, that gap is valuable information. It usually means the story is ambiguous, under-specified, or hiding a dependency nobody has mentioned yet — and it's far cheaper to find that out before the sprint starts than halfway through it.

How a planning poker session works

• Pick a story from the backlog

  The product owner or facilitator reads out (or shares) the story under discussion, including its acceptance criteria.

• Ask questions

  The team asks whatever they need to understand the scope — this is often where the real value of the session shows up, independent of the final number.

• Vote privately

  Everyone picks a card — physical or digital — without seeing anyone else's choice.

• Reveal together

  All votes are shown at once. If everyone agrees, the estimate is set and the team moves on.

• Discuss the outliers

  If votes diverge, the highest and lowest voters explain their reasoning, then the team re-votes. Two or three rounds is normal; more than that usually means the story needs to be split.

The card values

Most planning poker decks use a Fibonacci-like sequence — 1, 2, 3, 5, 8, 13, 20, 40, 100 — rather than a linear 1-through-10 scale. The gaps get wider as the numbers get bigger on purpose, because the team's confidence in a precise estimate gets wider too. A deck usually also includes a ? card for "I genuinely don't know" and sometimes a coffee cup for "let's take a break." The reasoning behind the specific sequence — and why teams shouldn't just use hours instead — is covered in more detail in how to estimate story points.

Planning poker online vs. in person

A physical card deck works fine when the whole team is in one room. It falls apart the moment even one person joins remotely — there's no way for them to hold up a card the rest of the room can see, and no simultaneous reveal without someone reading numbers out loud, which reintroduces the exact anchoring problem the technique exists to prevent.

Online planning poker tools solve this by replacing the physical deck with a session link: every participant joins from their own browser, votes privately, and the tool reveals all votes at the same instant regardless of where anyone is sitting. It also keeps a record — per-story and per-team statistics on how estimates trend over time, which a paper deck simply can't do. For teams that are partly or fully distributed, see planning poker for remote teams.

Works with your existing tools

StoryPointCards can connect to a team's Jira Cloud site to import backlog issues straight into a session instead of retyping them, and once a story is pointed, the agreed estimate can sync back to the linked Jira issue automatically. It's an optional, per-team connection managed from team settings — nothing is shared with Jira until a team chooses to connect it.

Common mistakes to avoid

The most common failure mode is treating story points as disguised hours — assigning a fixed hours-per-point conversion and then holding the team to it. That defeats the purpose of a relative scale and turns estimation sessions into a negotiation instead of a discussion. The second most common mistake is skipping the discussion round entirely when votes match, even when the story itself was rushed through without real understanding. The vote converging isn't the goal — shared understanding of the work is, and the vote is just how you find out whether you have it.

Frequently asked questions

What is planning poker?

Planning poker is a consensus-based estimation technique where every member of a scrum team privately picks a card representing their estimate for a story, then reveals it at the same time. It's used to size backlog items in story points before a sprint.

Why do teams reveal estimates at the same time?

A simultaneous reveal stops the first person to speak from anchoring everyone else's number. Anyone can call out a story point estimate before a group discussion, and the rest of the team unconsciously drifts toward it. Planning poker removes that bias by design.

Can planning poker be played online?

Yes. Online planning poker tools replace the physical card deck with a shared session link: everyone joins from their own browser, picks a card, and the tool reveals every vote at once. This works as well for remote teams as it does for a team sitting in the same room.

Is planning poker free?

The technique itself needs nothing but a deck of cards. Most online planning poker tools, including StoryPointCards, offer a free tier that covers the core workflow: create a session, vote, and see results.