Planning poker for remote teams

New to the technique itself? Start with what is planning poker for the fundamentals, then come back here for how to run it with a team that isn't in the same room.

Why estimating over a call quietly breaks

A video call amplifies the exact forces planning poker exists to neutralize:

• Anchoring gets worse. On a call there is usually one person talking at a time, so the first estimate spoken lands with even more weight. Everyone else adjusts toward it instead of forming an independent view.
• Turn-taking hides disagreement. Interrupting politely over video is hard, so quieter people simply agree to keep things moving. Their doubts, which are often the most valuable signal, never surface.
• Attention leaks. A muted, camera-off participant reading email is invisible. When the session is a round of open discussion, it is easy to check out and rubber-stamp whatever the group lands on.

A private vote followed by a simultaneous reveal fixes all three at once. Everyone has to commit to a number before seeing anyone else's, so there is nothing to anchor on, no way to quietly abstain, and every disagreement becomes visible the moment the cards flip.

What an online room replaces

In a physical session the deck of cards does the work: people hold their choice face down, then turn it over together. An online planning poker room replaces that deck, and only that deck. Everyone still needs to be talking, whether that is a video call, a voice channel, or people sitting in two offices on one line. The room handles the part a call cannot: it keeps each vote hidden until the reveal, then shows every card at the same instant.

That is the one feature to insist on. A shared spreadsheet or a chat thread cannot hide the first number, and once it is visible the estimate is already contaminated. If a tool reveals votes as they arrive, it is not planning poker; it is a poll with extra steps.

How to run a remote session

1. Refine the backlog before the call. Add the items to estimate ahead of time so the live session is spent voting, not reading. A shared queue of items keeps the session moving from one to the next without hunting for the next ticket.
2. Get everyone into the same room. Share one link. Whoever is facilitating opens the room, and each estimator joins from their own device. Observers, such as a product owner or a stakeholder watching, join too but sit out the voting.
3. Present one item, briefly. Someone who knows the item explains it in a sentence or two, and the team asks clarifying questions. Keep it short; this is not the design meeting.
4. Everyone votes privately. Each person picks a card. Nobody sees the others, and nobody knows who has and hasn't voted beyond a simple confirmed indicator.
5. Reveal together. Once everyone has confirmed, the cards flip at once. If the numbers agree, record the estimate and move on. If they don't, the highest and lowest estimators explain their thinking, and you vote again.
6. Move to the next item. Most items settle in a round or two. Pull the next one from the queue and repeat.

Keeping a remote session fast

The failure mode of remote estimation is not bad estimates; it is a session that drags until people disengage. A few habits keep it tight:

• Timebox the discussion. A couple of minutes per item is plenty. Anything that turns into a design debate gets parked and taken offline, not estimated on the spot.
• Let the reveal happen on its own. Waiting for the facilitator to click reveal after everyone has already voted is pure dead time. Auto-reveal turns the cards over the moment the last person confirms.
• Use a short reveal timer when discussion is the goal. A brief delay before the cards can be shown gives everyone a moment to actually think, rather than copying the first person who votes.
• Don't re-vote forever. After two or three rounds without convergence, either take the higher number and move on, or treat the disagreement as a sign the item needs splitting or clarifying before anyone works on it.

Live or async?

You can collect a first round of votes asynchronously, and for a small, well-understood backlog that is sometimes enough. But the estimate is not the real output of planning poker; the conversation a spread of estimates starts is. That conversation is hard to have well in comments spread across a day and several time zones, where tone is lost and replies arrive hours apart.

The reliable pattern for distributed teams is to split the work: refine and clarify items asynchronously, then estimate live in a short, focused session. Even thirty minutes of real overlap beats a day of threaded back-and-forth, because the disagreements get resolved while everyone is present to resolve them.

Common questions

Do you need a special tool for remote planning poker?

You need something that hides votes until everyone has chosen and then reveals them at once. A shared spreadsheet or chat cannot do that, because the first number posted anchors everyone else. A dedicated online room handles the private vote and simultaneous reveal for you, which is the whole point of the technique.

Should cameras be on during remote estimation?

Cameras help you read hesitation and confusion that a voice call hides, so they are worth keeping on for the discussion. They are not required to vote, though. The estimate comes from the cards, not from faces, so nobody is penalized for turning a camera off.

Can planning poker be done asynchronously?

You can gather first-round votes asynchronously, but the value of planning poker is the conversation that a spread of estimates starts. That conversation is hard to have well in comments across time zones. Prepare and refine items async, then estimate live, even if live is only a short focused call.

How do you keep a remote session from dragging?

Timebox discussion per item to a few minutes, estimate one item at a time, and let the cards reveal as soon as everyone has confirmed instead of waiting on one person. A reveal timer and auto-reveal remove the most repetitive stalls, and anything that turns into a design debate should be parked, not estimated.

What about distributed teams across time zones?

Find one overlapping hour and protect it for estimation, because a live reveal is worth more than perfectly convenient scheduling. Keep the sessions short and frequent rather than long and rare, and use an async backlog refinement pass beforehand so the live time is spent voting, not reading.

Try it with your remote team

Point Taken is a free planning poker room built for exactly this: live voting, cards that stay hidden until the reveal, an optional reveal timer and auto-reveal to keep sessions moving, and nothing between your team and an estimate. No sign-up, no ads, no tracking. Open a room, share the link, and start with your next backlog item.