What Is Planning Poker?

Planning poker — also called scrum poker or pointing poker — is a technique agile teams use to estimate the relative effort of user stories, bugs, and technical tasks. Instead of one person assigning hours or story points while everyone else listens, each team member selects an estimate independently, all votes are revealed at the same time, and the group discusses differences before agreeing on a final value.

The method was popularized by Mike Cohn and draws on the Delphi estimation technique: independent judgment first, then structured discussion. That sequence matters because it reduces anchoring bias — the tendency for people to adjust their estimates toward the first number they hear.

How a planning poker round works

A typical round follows a repeatable pattern that works in person with physical cards or online with a tool like PlanITPoker:

1. The Product Owner or facilitator presents one backlog item.
2. The team asks clarifying questions until scope is understood.
3. Each participant selects an estimate card privately.
4. On the facilitator's signal, everyone reveals their card simultaneously.
5. If estimates differ widely, the highest and lowest voters explain their reasoning.
6. The team re-votes until estimates converge or the facilitator calls the value.

The goal is not perfect precision on the first vote. The goal is shared understanding: when two engineers pick 3 and 13 for the same story, that gap usually means hidden complexity, missing acceptance criteria, or different assumptions about implementation.

Why agile teams use planning poker

• Reduces anchoring bias — Private votes and simultaneous reveal prevent the senior developer's estimate from dominating the room.
• Surfaces unknowns early — Wide spreads signal stories that need refinement before sprint commitment.
• Builds shared ownership — Everyone participates, not just the tech lead or Product Owner.
• Works for remote teams — Online rooms replicate the same flow without passing physical cards around a table.
• Supports relative estimation — Story points compare effort to past work rather than guessing calendar hours.

When to use planning poker

Teams most often run planning poker during sprint planning and backlog refinement. Sprint planning focuses on stories the team will commit to for the upcoming iteration; refinement prepares future stories so estimation moves faster when those items reach the top of the backlog.

Planning poker is less useful for tasks that are already broken down to hours, fully specified tickets with fixed deadlines, or work owned by a single specialist who does not need team consensus. It shines when multiple disciplines contribute to delivery and when uncertainty is still present.

Common estimation decks

Most teams use a Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34) because larger gaps at higher numbers reflect increasing uncertainty. Some teams prefer T-shirt sizes (XS–XL) for early roadmap sizing before converting to story points. PlanITPoker supports both decks plus question (?) and coffee break cards. Read our guides on Fibonacci estimation and T-shirt sizing for deck selection advice.

Planning poker vs other estimation methods

Single expert estimate: Fast but fragile — one person's blind spots become the plan. Hour-based task breakdown: Feels precise but ignores team velocity differences and interrupts flow with false accuracy. Planning poker: Balances speed with team input and creates a record of discussion, not just a number.

Run planning poker online for free

PlanITPoker lets you create a room instantly, share a link or QR code, add stories, vote with Fibonacci or T-shirt decks, and view vote distributions — no account required. For facilitation tips, see our planning poker best practices guide.