What Is Planning Poker? A Beginner's Guide to Agile Estimation

Table of Contents

If you’ve just joined an agile team, you’ve probably heard someone say “let’s planning poker this one” and watched everyone reveal a number at the same time. If it looked a little like a card game, that’s because it is one. Here’s what’s actually going on—and how to run your own session in a couple of minutes.

What Is Planning Poker?

Planning poker (also called scrum poker) is a consensus-based estimation technique used by agile teams to size up work. Instead of one senior dev guessing how long a task will take, everyone estimates at the same time, then the team talks through any disagreement.

The “poker” part comes from the cards: each person picks a card representing their estimate and reveals it simultaneously, so nobody is influenced by what anyone else says first.

Why Not Just Have the Lead Estimate Everything?

Because the person who shouts a number first anchors everyone else. The moment someone says “that’s a two-day job,” the rest of the room quietly recalibrates around two days—even if half of them were thinking a week.

Planning poker fixes this with one simple rule: estimate privately, reveal together. It gives you two things:

  • 🧠 Independent judgement — no anchoring on the loudest voice in the room
  • 💬 Productive disagreement — when a 3 and a 13 land next to each other, that gap is the conversation worth having

That gap is the real value. A wide spread almost always means someone knows about a hidden complication—or someone has misunderstood the story.

How a Round Actually Works

A single round is quick:

  1. Read the story. The product owner reads out a user story or task and answers questions.
  2. Everyone votes at once. Each team member privately picks a card.
  3. Reveal together. All cards flip at the same time.
  4. Discuss the outliers. The highest and lowest estimators explain their reasoning.
  5. Re-vote. Estimate again now that the hidden context is on the table.

You repeat until the team converges. Most stories settle in one or two rounds.

What Are the Numbers?

The cards usually aren’t a normal 1–10 scale. The most common deck is the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21…), because the growing gaps reflect a simple truth: the bigger a task is, the less precisely you can estimate it. There’s a real difference between a 1 and a 2, but “is this a 20 or a 21?” is a meaningless question.

Other teams prefer T-shirt sizes (S, M, L, XL) for lighter-weight estimation, or powers of 2 (1, 2, 4, 8, 16). They all share the same idea: relative sizing, not exact hours.

Tips for Your First Session

  • Estimate effort, not hours. Planning poker measures relative size, not a calendar.
  • Timebox the discussion. Two minutes of debate per story, then re-vote.
  • Don’t average the votes. A 3 and an 8 isn’t a 5.5—it’s a conversation.
  • Keep it remote-friendly. Simultaneous reveals matter even more when you can’t read the room.

Run Your First Round in 30 Seconds

You don’t need an account, a trial, or a credit card to try it. Head to Planfree.dev, click Create Room, share the link with your team, and start estimating. It’s free, has no participant limits, and supports Fibonacci, T-shirt, and powers-of-2 decks out of the box.


Planfree.dev is open-source and actively maintained. Star or contribute on GitHub, or drop a feature idea via the in-app chat.

Share :
comments powered by Disqus

Related Posts

Planning Poker Without the Pain: How Planfree.dev Became Our Go-To Tool

You know that feeling: sprint planning is about to start, you open the planning poker tool, and… it wants you to log in. Then it asks for a team plan. And suddenly your focus is gone.

Read More

Why Planfree.dev Is the Best Free Planning Tool for Developers

In the world of agile development, effective sprint planning is crucial. But too often, the tools we use are bloated, locked behind subscriptions, or cluttered with features we don’t need. That’s where Planfree.dev comes in—a completely free, no-nonsense planning poker tool built for developers who just want to get things done.

Read More

I Needed a Planning Tool That Didn’t Suck — So I Built Planfree.dev

Every sprint, our team would groan when it was time to do estimations. Not because of the work—but because of the tools.

Read More