What is Planning Poker?

Why story points instead of hours?

Hours are deceptive. Two developers can estimate the same task very differently based on their experience. Story points sidestep this problem by measuring relative effort and complexity — not calendar time.

When a team agrees that Story A is a "3" and Story B is an "8", they're not saying B takes 8 hours. They're saying B is roughly 2.5× more complex. Over time, a team's velocity (story points completed per sprint) becomes a reliable planning tool.

How does a planning poker session work?

1. Select a story. The product owner or facilitator presents a user story to the team.
2. Discuss briefly. Team members ask clarifying questions. The goal is shared understanding — not agreement yet.
3. Vote simultaneously. Everyone picks a card and reveals their estimate at the same time. This prevents anchoring bias.
4. Discuss outliers. If estimates differ significantly, the highest and lowest estimators explain their reasoning.
5. Re-vote (if needed). After discussion, the team votes again until consensus is reached.
6. Record the estimate. The agreed story point value is locked in and you move to the next story.

Why the Fibonacci sequence?

Most planning poker decks use the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21…

The growing gaps between numbers reflect a fundamental truth: the larger a task, the less precise our estimate. Trying to distinguish between "14 hours" and "15 hours" for a complex feature is meaningless. The Fibonacci scale forces teams to acknowledge that uncertainty grows with complexity.

Some teams use a simplified scale (1, 2, 3, 5, 8, 13) or a T-shirt size system (XS, S, M, L, XL). Estimr supports custom card sets, so you can use whatever works for your team.

What do the special cards mean?

• ☕ (coffee cup / break) — "I need a break before I can estimate properly."
• ? (question mark) — "I don't have enough information to estimate this story."
• ∞ (infinity) — "This story is too large to estimate. It needs to be broken down."

These cards prevent false consensus. If half the team plays ☕ or ?, that's a signal — not an obstacle.

Digital vs. physical planning poker

Physical card decks work great in a room. For remote and hybrid teams, digital tools like Estimr offer several advantages:

• No cards to buy, print, or distribute
• Instant simultaneous reveal — no risk of peeking
• Automatic consensus detection
• Persistent session history and CSV export
• No account required for participants — just share a link
• Works in any browser, on any device

Common mistakes to avoid

• Anchoring: Don't reveal estimates sequentially — everyone should vote at the same time.
• Estimating tasks, not stories: Estimate user value and complexity, not implementation steps.
• Skipping discussion: The conversation after a split vote is often more valuable than the final number.
• Over-refining small stories: If a story is clearly a "1" or "2", don't spend 10 minutes on it.
• Ignoring velocity: Track your team's actual velocity and use it to calibrate future estimates.