Remote planning poker works. In some ways it works better than in-person sessions — because the tool forces simultaneous reveals, removes the pressure of a physical room, and gives quieter team members an equal voice. But it requires a different setup than gathering around a table with physical cards.
Here is what to do differently when your team is distributed.
The one thing that matters most: synchronous reveal
The entire value of planning poker depends on everyone revealing at the same time. In an in-person session, you flip cards simultaneously. Remotely, you need a tool that holds everyone's votes hidden until a moderator triggers the reveal.
Doing this over Slack, a shared spreadsheet, or a video call where people say their number one at a time does not work. The first number anchors every vote that follows, which is exactly the bias planning poker is designed to prevent.
A dedicated planning poker tool solves this automatically. Everyone votes privately, cards flip together, discussion happens from a level playing field.
Keep video on during the reveal
The reveal moment is where the session earns its value — you see who voted high, who voted low, and the genuine reactions that follow. With cameras off, you lose all of that. Ask your team to keep video on at least during the reveal and the discussion that follows, even if they turn it off during quieter moments.
Shorter sessions, more frequently
Remote estimation fatigue hits faster than in-person fatigue. In-person, a 90-minute refinement session is manageable. Remotely, 45 minutes is closer to the limit. Rather than trying to estimate your entire sprint backlog in one session, split it into two shorter ones on different days.
A good rule: stop after 8–10 stories regardless of how much time is left. Beyond that, the estimates stop reflecting careful thinking and start reflecting exhaustion.
Make the backlog visible to everyone
In a physical room, the Product Owner can point at a card or a whiteboard. Remotely, you need everyone looking at the same screen. Share your Jira, Linear, or Notion board before the session starts, and call out the exact item being estimated by name before each vote.
Never assume everyone is looking at the same thing. Remote ambiguity about which story is being estimated is one of the most common causes of wild estimation spreads.
Handle time zones explicitly
If your team spans more than two time zones, planning poker sessions require deliberate scheduling. The worst outcome is a session where half the team is fresh in the morning and the other half is at 7pm after a full day. Estimates from tired people skew differently.
Rotate session timing fairly if the time zone spread is large. A team where one side always gets the bad end of the schedule will have worse estimates — and lower morale.
Give quieter team members a way in
Remote sessions tend to amplify existing team dynamics. The people who dominate in-person discussions will dominate video calls even more. The people who stay quiet in the room will stay even quieter online.
Planning poker structurally helps here — because everyone votes, everyone has an opinion on record before anyone speaks. But make a habit of asking the low voter first, then the high voter. Not the loudest person.
What you need to run remote planning poker
- A video call — any platform works: Zoom, Meet, Teams
- A planning poker tool — PlanPok requires no account; share the link before the call
- A shared backlog view — screen share or a link everyone can open
- A moderator — someone who reads stories, triggers reveals, and keeps time
That is all. No special hardware, no setup call, no plugins. The simplest remote planning poker sessions are often the most effective ones.