How to run planning poker remotely: a facilitator’s guide

Planning poker was designed for a room full of people holding paper cards. Remote teams lose the cards, but they keep the hard part: getting five to fifteen people to agree on a number without the loudest voice deciding it.

This guide is for whoever runs the session. It covers what to prepare, how to run each round, and the small habits that keep a remote estimation meeting under an hour.

Why planning poker works (and what remote breaks)

The method has one core rule: everyone picks a card in secret, then all cards are revealed at once. That rule does two jobs:

• It stops anchoring. If the tech lead says “that’s a 3” first, most people drift toward 3.
• It surfaces disagreement. When one person shows 2 and another shows 13, they know something different about the work. That conversation is the real value of the meeting.

On a video call, it’s easy to lose both. People type numbers into chat one by one, so later voters see earlier votes. Or the facilitator asks “any objections?” and silence counts as agreement. A remote session needs a tool that hides votes until the reveal, and a facilitator who protects the discussion.

Before the session

Prepare a short, ready backlog

Bring stories that are ready to estimate: a clear title, a description, and acceptance criteria. A story the team can’t understand in two minutes isn’t ready for estimation. It needs refinement first.

A good target is 8 to 15 stories per hour. If you bring 40, the team will rush the last 30 and the numbers will be noise.

Choose a deck in advance

Decide on the scale before the meeting, not during it:

• Fibonacci (0, 1, 2, 3, 5, 8, 13, 21) is the common default for story points.
• T-shirt sizes (XS to XXL) suit early roadmap sizing, when details are fuzzy.
• Modified Fibonacci (adds ½, 20, 40, 100) helps if your backlog mixes tiny tweaks and big epics.

If you’re unsure, read Fibonacci vs T-shirt sizing for a longer comparison.

Set up the room

With Planning Poker, you create a room, pick the deck and share the link. Nobody needs an account. People open the link, type a name and they’re in. For a sensitive backlog, add a room password and send it in a different channel from the link.

If several teams estimate together, for example frontend, backend and QA, turn on teams when you create the room. Everyone picks a team when they join, and the results show a median per team as well as the overall result.

You can also paste the stories into the room’s queue beforehand: Jira keys, links or titles, one per line. The queue then walks you through them in order.

Running a round

Each story follows the same short loop. Keep it boring and predictable; that’s what makes it fast.

1. Read the story aloud. The product owner reads it and answers clarifying questions. Cap this at about two minutes.
2. Everyone votes in secret. Others only see that you voted, never what you voted. People can change their card until the reveal.
3. Reveal. The facilitator reveals once everyone has voted, or turns on auto-reveal so the cards flip as soon as the last vote is in.
4. Discuss the spread. If the votes are close, take the consensus and move on. If they’re far apart, the highest and lowest voters explain their reasoning. The tool marks these outliers with talks first, so you don’t have to call people out by name.
5. Re-vote once if needed. After the discussion, run one more round. If the team still disagrees, take the higher estimate or split the story. Don’t let one story eat fifteen minutes.

Use the ☕ and ? cards

Every deck includes ? (“I don’t understand this story”) and ☕ (“I need a break”). Take them seriously. Several ? cards mean the story isn’t ready; send it back to refinement instead of forcing a number. A ☕ after 45 minutes means you should stop or take five.

Remote-specific habits that help

• Cameras on during discussion, if your team is comfortable with it. Disagreement is easier to resolve when people can see each other.
• One shared screen, or none. The room itself shows the story, the votes and the stats to everyone, so you don’t need to screen-share.
• Let observers watch, not vote. Stakeholders and managers can join as spectators. They see everything, but their presence doesn’t skew the stats, and they’re less tempted to suggest a number.
• Keep sessions short. Estimation quality drops after about an hour. Two 45-minute sessions beat one 90-minute marathon.
• Plan for flaky connections. If the facilitator drops off the call, the room shouldn’t die with them. In Planning Poker, the person who joined earliest takes over as host automatically, and the current round is kept.

After the session: record the estimates

Estimates are only useful if they reach your tracker. Each revealed story goes into the session log. You can download it as CSV or copy it into Jira, Linear or a doc.

If you used Jira keys in the queue, you can also export a Jira-ready CSV with the issue key and story points, and a column per team if you estimated by team. Import it with Jira’s CSV importer to update the points in bulk.

Rooms only exist while someone is in them. Download the log before the last person leaves.

A one-page checklist

Before

• 8–15 ready stories, with acceptance criteria
• Deck chosen (Fibonacci by default)
• Room created, link and optional password shared
• Teams set up if more than one discipline estimates

During

• Read the story, two minutes of questions
• Secret vote, then reveal
• Outliers talk first
• At most one re-vote, then decide or split

After

• Export the log or Jira CSV
• Send unclear (?) stories back to refinement

Ready to try it? Start a free room. It takes about ten seconds, and your team doesn’t need to sign up.