Scrum Poker

Run a focused Planning Poker session with private votes, live reveals, flexible decks, and clear facilitator controls.

Loading tool...

Getting started

  1. Choose a display name and avatar so teammates can recognize your vote card.
  2. Create a room when you are facilitating, or paste a room code from a teammate to join an existing session.
  3. Copy the shareable room URL from the Room panel and send it to everyone who should estimate.
  4. Enter the current backlog item title before voting so the result is tied to the right discussion.
  5. Ask each participant to choose a card. Votes stay private until a facilitator reveals them.
  6. Discuss the result, agree on the estimate, then use Next backlog item to reset voting for the next item.

How Scrum Poker works

Scrum Poker, also called Planning Poker, is a lightweight way for a team to estimate work without letting the first loud opinion set the number. Everyone selects an estimate privately, the facilitator reveals all votes at the same time, and the team uses the spread to find hidden assumptions.

The goal is not to make story points mathematically perfect. The useful part is the conversation: a small estimate can reveal a simpler implementation path, while a large estimate can reveal risk, missing requirements, or work that should be split before sprint planning.

Facilitator controls worth knowing

  • Decks: use Fibonacci for story points, Linear for small numeric estimates, and T-shirt sizes for rough sizing.
  • Reveal mode: Manual keeps votes hidden until a facilitator reveals them; Auto reveal opens results once every connected member has voted.
  • Voting progress: the hidden board shows who has voted, who is still waiting, and a donut that fills until everyone is ready.
  • Result views: switch between bubble, bar, donut, pie, and polar charts to spot agreement, outliers, and ties.
  • Roles: the room creator can promote facilitators, demote them, or remove members who joined the wrong room.
  • Backlog history: previous items stay visible with vote counts and revealed results, and a facilitator can revote an item when the discussion changes.

Run a cleaner estimation conversation

  • Estimate relative complexity, uncertainty, and effort instead of treating cards as exact hours.
  • Keep the first vote silent. Reveal first, then discuss, so nobody anchors the room early.
  • When estimates are far apart, ask the high and low voters what they assumed before voting again.
  • Use ? when the item is not clear enough to estimate, and Coffee when the team needs a short break.
  • Split work that repeatedly gets large or scattered estimates; the spread is often more useful than the average.
  • Record the final agreed estimate in your backlog tool after the conversation. This room is a facilitation aid, not a permanent project record.

FAQ

What is Scrum Poker?

Scrum Poker is a team estimation technique for Scrum and agile planning. Each participant chooses an estimate privately, then the team reveals all votes together and discusses differences before agreeing on a final estimate.

Why should votes stay hidden before reveal?

Hidden votes reduce anchoring. A senior voice, early number, or confident guess can pull the whole team toward one answer before quieter participants have shared their own view.

Which deck should I choose?

Use Fibonacci when you want classic story point estimation with bigger gaps as uncertainty grows. Use Linear for small, concrete work. Use T-shirt sizes when the team only needs rough relative sizing.

Who can reveal votes or edit the backlog item?

The room creator and promoted facilitators can reveal or hide votes, start the next backlog item, edit the active item title, and change room settings. Regular members can join, update their name or avatar, and vote.

What happens if the facilitator changes the deck?

Changing the deck clears the current votes and hides results, because some selected values may not exist in the new deck. Change decks before the team starts voting whenever possible.

What do ? and Coffee mean?

? is useful when the item is too unclear to estimate. Coffee is a pause signal. Treat both as conversation signals rather than numeric estimates.

How long does a room stay available?

Rooms are kept in memory and inactive rooms are closed after one day. Use the room for the live session, then save the agreed estimates in your normal backlog or issue tracker.