What Is Pointing Poker in Agile Estimation
Pointing poker is a collaborative estimation game that agile teams use to assign story points to their work. Members vote on the effort each task needs, then reveal their cards together. The name comes from the points the team assigns, which measure relative size rather than hours.
The technique keeps estimation fair by hiding votes until the reveal. That structure stops one confident voice from setting every number and gives quieter members an equal say in the outcome.
What Is Pointing Poker?
Pointing poker is an estimation method where each team member scores a user story with a card. The cards usually follow the Fibonacci sequence, so the values grow as uncertainty rises. Everyone reveals at once, which keeps each vote independent.
The goal is a shared estimate the team trusts. By discussing the highest and lowest votes, members align on scope and surface risks. The method suits Scrum and Kanban teams that plan work in repeatable cycles.
How Is Pointing Poker Different From Planning Poker?
Pointing poker and planning poker describe the same technique. Both names refer to the card-based estimation game where teams assign story points to work. The word pointing emphasizes the story points, while planning emphasizes the sprint planning context.
- Same ritual: private votes, simultaneous reveal, open discussion.
- Same goal: a shared, relative estimate for each story.
- Same tools: a card deck or a browser-based room.
How Do You Run a Pointing Poker Session?
A pointing poker session is quick once the team knows the loop. The facilitator keeps the round moving so estimates converge without long debates.
Many teams run the round in a free pointing poker room so remote members vote in real time. A typical session follows these steps.
- The facilitator presents the next user story.
- The team clarifies scope and acceptance criteria.
- Each member selects a point value privately.
- All cards reveal at the same time.
- Outliers explain their reasoning, then the team re-votes.
Pointing Scales Teams Use
Teams pick a scale that matches how they think about effort. The table below shows the common pointing scales and where each one fits.
| Scale | Example Values | Typical Use |
|---|---|---|
| Fibonacci | 1, 2, 3, 5, 8 | Standard story point estimation |
| Modified Fibonacci | 0.5, 1, 2, 3, 5, 8, 20 | Teams needing finer low-end detail |
| T-shirt | S, M, L, XL | Rough sizing of an early backlog |
Tips for Accurate Pointing
Accurate pointing comes from consistent habits, not from chasing a perfect number. The tips below keep estimates reliable over time.
- Compare new stories to a known reference story.
- Estimate relative effort, never raw hours.
- Re-vote whenever the spread is wide.
- Record assumptions so future sprints stay consistent.
Pointing Poker for Distributed Teams
Remote teams need a shared room where votes stay hidden until the reveal. A real-time tool keeps distributed members aligned without spreadsheets or chat threads.
- One link brings the whole team into the same room.
- Hidden votes preserve independent judgment.
- Instant statistics highlight disagreement at a glance.
Frequently Asked Questions
Why is it called pointing poker?
It is called pointing poker because teams assign story points during the game. The poker part refers to the hidden cards that members reveal together, much like a poker hand. The name highlights the points, while planning poker highlights the sprint planning context, but both describe the same estimation method.
What are story points in pointing poker?
Story points are a unit of relative effort that combines complexity, uncertainty, and workload. They do not map directly to hours. A five-point story is roughly five times the effort of a one-point story. Teams use story points so estimates stay stable even when individual speeds differ across members.
Can pointing poker work without physical cards?
Yes. A browser-based tool replaces physical decks with digital cards. Scrum Poker lets members vote from any device with no sign-up, and the reveal happens for everyone at once. This makes pointing poker practical for remote and hybrid teams that cannot share a single table.
How do we handle big disagreements in votes?
When votes spread widely, ask the highest and lowest voters to explain their thinking. Often one side sees a risk the others missed. After a short discussion, the team re-votes. Repeat until the estimates converge, which usually happens within two rounds once the scope is clear.
