Free Scrum Poker App for Sprint Planning

Start a scrum poker room here: add your name, pick a deck and share the link with your team. Everyone picks a story point card in private, all the cards turn over together, and the team talks about the gap before it agrees a number. It runs online in any browser, with nothing to install.

Scrum poker and planning poker are the same ceremony under two names: the team sizes work relatively, votes simultaneously, and talks only about the gaps.

Rooms hold up to 20 people including facilitators, which covers a full scrum team plus product, design, and QA in one session.

Where scrum poker fits in the sprint

The ceremony earns its time in the two places where the team has to agree on size before it commits to anything.

Backlog refinement — size the items coming up, and find the ones whose acceptance criteria are too thin to size at all.
Sprint planning — work the queue, and leave with a sprint the whole team has actually agreed to rather than one the loudest voice set.
Mid-sprint, when a story turns out bigger than it looked — re-size it as a team instead of letting one person absorb the surprise.

What a scrum poker tool has to get right

Most of the value is in the reveal. Everything else is logistics.

Simultaneous reveal — if one estimate lands before the others, the rest drift toward it. That bias is the whole reason the ceremony exists.
A facilitator who does not vote — the Scrum Master or whoever runs the room needs to watch the spread, not add to it.
A spread that is visible, not averaged away — a 3 against a 13 is the useful part of the session, and averaging it hides the disagreement.
A join flow with no account — a guest who has to sign up before voting is a guest who joins five minutes late.

Choosing a scrum poker deck

Point Poker has three decks. You pick one when you create the room, and it stays fixed for the session so every vote is on the same scale.

Fibonacci (1, 2, 3, 5, 8, 13, 21, 34): the usual choice for story points. The gaps widen as items grow, which matches how uncertainty grows with size.
T-shirt sizes (XS to XXL): useful for epics and early roadmap sizing, where a number would suggest more precision than anyone has.
Powers of 2 (1, 2, 4, 8, 16, 32): a simple doubling scale for teams that find the Fibonacci jumps awkward.
Every deck has a ? card for anyone who cannot size the item yet. A table full of question marks means the story needs more work before anyone estimates it.

Running the session without it overrunning

Estimation meetings sprawl when the discussion has no stopping rule. These are the ones that hold.

Size relative to a story everyone remembers, not in hours. Pick that baseline before the first vote.
Discuss the outliers only. If the table is within one card of each other, record it and move on.
Time-box the discussion, then re-vote. A second vote after two minutes of context beats ten minutes of debate.
A story nobody can size is a finding, not a failure — send it back for splitting rather than guessing at it.

How scrum poker works, step by step

The Product Owner reads the story and answers questions about intent. Nobody names a number yet.
Everyone who will do the work picks a card privately. The cards stay hidden until the whole table has voted.
All the cards turn over at once, so no estimate can pull the others towards it.
If the votes sit within one card of each other, record the number and move on. If they spread, the highest and lowest voters explain what each of them is seeing.
Vote once more. If the table still splits, the story is too vague or too big: split it or send it back to refinement rather than averaging.

Frequently asked questions

What is scrum poker?

Scrum poker is a consensus estimation technique where each member of a scrum team privately picks a card representing the relative size of a backlog item, everyone reveals at once, and the team discusses the disagreements before agreeing a number. It is the same practice as planning poker — scrum teams simply tend to call it scrum poker.

Does the Scrum Guide require planning poker?

No. The Scrum Guide does not mention planning poker, story points, or any specific estimation technique — it only says the Developers size the work. Scrum poker is a widely used convention that fits Scrum well, not a rule you are failing to follow if you estimate some other way.

Who should take part in scrum poker?

Everyone who will do the work votes — developers, QA, and anyone else delivering the item. The Product Owner answers questions about intent but does not usually vote, since they are not estimating their own effort. The Scrum Master facilitates and stays out of the voting entirely.

What do you do when the team cannot agree on an estimate?

Ask the highest and lowest voters to explain what they are seeing — they are usually looking at different work. Then re-vote. If a second round still splits the table, the story is generally too vague or too large, and splitting it is a better outcome than settling on a middle number nobody believes.

How long should a scrum poker session take?

Around a minute or two per item once the team has a baseline, so a refinement session of ten to fifteen items fits comfortably in half an hour. Sessions that run long are usually a symptom of items arriving without acceptance criteria, not of the estimation itself being slow.

Does everyone need an account to join?

No. Anyone with the room link can join and vote from a browser, on desktop or mobile. A free account is only needed to reserve two permanent Team Room URLs for your team and to keep your sprint history.

Can we run scrum poker alongside Jira or Microsoft Teams?

Yes, and there is nothing to install. Paste your backlog items into the room in one go, share the room link in your Teams, Slack or meeting chat, and export the agreed estimates as CSV to bulk-update Jira, Linear or Azure DevOps. There is no plugin or integration to get approved.