How to Run Planning Poker With a Remote Team: A Practical Guide

Planning poker was designed for a conference room — cards on a table, everyone flipping at once. Remote teams can run it just as well, and in some ways better: digital tools eliminate the "I saw your card" problem entirely. Here's how to run planning poker with a distributed team, step by step.

What planning poker is (60-second refresher)

Planning poker is a consensus-based estimation technique. The team discusses a backlog item, then everyone privately selects an estimate (usually from a Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21), and all cards are revealed simultaneously. Big disagreements trigger discussion; the team re-votes until estimates converge. The simultaneous reveal is the whole point — it prevents anchoring, where the first or loudest voice drags everyone else along.

What you need before the session

• A prioritized backlog with items refined enough to estimate
• A shared estimation tool — a free online planning poker room everyone can join from a browser, no signup ideally
• A video call running alongside for discussion
• A deck agreement: Fibonacci for story points, or t-shirt sizes (XS–XL) for rougher sizing
• A timebox: 60–90 minutes max

Running the session: step by step

1. Set up the room (5 min). Create the planning poker room and share the link in the meeting chat. Do a practice vote on something silly to check the mechanics.

2. Present the item (2–3 min). The product owner presents one backlog item: what it is, why it matters, constraints. Keep it tight.

3. Clarifying questions (2–3 min). Timebox strictly. If it needs more clarification, it's not ready — park it.

4. Vote silently and simultaneously. Everyone selects privately, facilitator reveals all at once. No "I'm thinking it's a 5" before the reveal.

5. Discuss the outliers (3–5 min). Ask the highest and lowest estimators to explain briefly. The low voter often knows a shortcut; the high voter sees a hidden risk.

6. Re-vote until convergence. Usually 2–3 rounds. If not, the item is genuinely uncertain — take the higher estimate or split it.

7. Record and move on. About 5–8 minutes per item keeps energy up.

Remote-specific tips

• Cameras on for discussion; use chat for "+1" instead of ten people unmuting.
• Name a facilitator, not the loudest engineer — and rotate the role.
• Mind time zones: schedule in the overlap window, keep sessions under 90 minutes.
• Async option for simple items: collect votes over a few hours, discuss only divergences live.

Common pitfalls

• Anchoring: enforce simultaneous reveal, no discussion before voting.
• Senior dev dominates: ask juniors to explain first.
• Hours instead of points: agree upfront that points measure relative complexity.
• Endless discussion: 3-round limit, then higher estimate or split.
• Estimating unready items: park it — poker is for estimation, not refinement.

FAQ

How many items per session? 8–12 in 60–90 minutes.
What if the team never agrees? After 2–3 rounds, take the higher estimate or split the item.
Should the product owner vote? Generally no — the PO presents the "what," the team estimates.
Can it work asynchronously? Yes for well-understood items; keep the hard ones synchronous.
What's a good free tool? Happy Backlog (https://happybacklog.com) offers free planning poker with no signup — plus 13 more Scrum Master tools (retro templates, standup generator, team roulette, sprint calculators).