One More Point

HomeBlogWhat Is Scrum Poker and Why Does Your Team Need It?
Cover illustration for "What Is Scrum Poker and Why Does Your Team Need It?"

What Is Scrum Poker and Why Does Your Team Need It?

Fundamentals2 min read

What Is Scrum Poker and Why Does Your Team Need It?

Scrum poker - also called planning poker - is a consensus-based estimation technique used by agile teams to size user stories. Instead of one person guessing or a manager dictating effort, the whole team estimates simultaneously, then discusses any disagreement until they reach alignment. For the complete rules, history, and facilitation guidance, see the full Scrum Poker guide.

How It Works

  1. The team reads a user story aloud.
  2. Each person privately selects a card representing their estimate (Fibonacci numbers like 1, 2, 3, 5, 8, 13 are common).
  3. Everyone reveals their cards at the same time.
  4. If estimates differ, the high and low estimators explain their thinking.
  5. The team re-estimates until they converge.

The simultaneous reveal is the key insight: it prevents anchoring, where the first number spoken tends to pull everyone else toward it.

Why Not Just Use a Spreadsheet?

Spreadsheets encourage a single "expert" to own estimates and everyone else to silently accept them. Scrum poker forces every engineer to think through the story independently. Junior developers often catch complexity that senior engineers have learned to ignore. Spectators become contributors.

What the Cards Mean

Most decks use a modified Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21. The gaps between numbers grow intentionally - anything above 13 is uncertain enough that breaking the story down is usually better than estimating it whole.

Special cards like "coffee break" and "too large to estimate" keep communication human. (If a story genuinely is too big to estimate, that's a signal to split it, not to argue about it.)

Getting Started

You don't need physical cards. Once you're ready to facilitate, the step-by-step guide to your first session covers setup and the mistakes first-timers make. One More Point lets your team run a session in seconds - create a room, share the link, and start estimating together, whether your team is in the same office or spread across time zones.

Fundamentals5 Common Planning Poker Mistakes (And How to Fix Them)Planning poker only works when the team trusts the numbers. These five mistakes quietly undermine that trust - and the fixes are simpler than you think.FundamentalsHow to Estimate Bug Fixes in Your BacklogBug fixes are notoriously hard to estimate because the scope is often unknown until you're in the code. Here's a framework for sizing them without wild guessing.FundamentalsSplitting User Stories Without Losing Estimation ValueSplitting stories to fit a sprint is easy. Splitting them so the pieces remain independently deliverable and estimable is harder. Here's how to do it right.

Ready to estimate together?

Start a free session and invite your team when you’re ready.