What breaks when you go remote
The magic of planning poker is independent voting. In a room, cards stay face-down on the table. On a video call, people type numbers in chat and the first one anchors everyone else. A real remote planning poker tool hides votes until every participant has voted.
The synchronous setup
For teams that can meet live (same timezone, or close enough to tolerate a 45–60 minute overlap):
- Schedule a 45-minute refinement slot once a week. Shorter than most teams think they need.
- Pre-import the backlog into a planning poker tool like Pokor — Jira, Notion, GitHub, or CSV.
- Run a short Q&A on each story, then vote. 90 seconds per story is a healthy cadence.
- Reveal together. If the spread is wide, the outliers explain first.
- Re-vote once. If you still can't converge, park the story for a spike or split it.
The async-friendly variant
For distributed teams with wide timezone gaps, a 100% synchronous ceremony is often the wrong shape. A hybrid pattern that works:
- Asynchronous voting window — open a Pokor session on Monday, everyone casts votes within 24 hours.
- Synchronous discussion — a 20-minute call for the stories with the widest spread. Skip anything where the team converged.
- Re-vote the contentious ones live after each discussion, then lock the estimate.
This trades some consensus-richness for a lot of hours back. It works particularly well for backlogs where most stories are routine and only a few have genuine ambiguity.
Set a per-story voting window when you create the session — teammates vote on their own time from a single-story focused page, rationale and confidence included.
Where the chat integration earns its keep
Opening a new tab is friction. Remote teams that already live in Slack or Discord get better attendance when the session launches from chat with a single join button. /pokor in the channel, posts a message with "Join as Organizer", the organizer accepts, the rest of the team clicks through — done.
Camera-on, cards-hidden
Turn cameras on during the Q&A and discussion — it's the fastest signal for "I'm confused but don't want to interrupt." Then let the tool handle the voting: hidden cards, simultaneous reveal, no chat spoilers.
Mistakes that kill remote sessions
- Open voting in Slack. "Drop your number in the thread" is not planning poker. It's first-mover anchoring with extra steps.
- Voting on stories nobody has read. Remote attention is thin. If you haven't pre-shared the backlog, the meeting is a read-aloud, not an estimation session.
- No timebox. Wide-spread stories will eat the entire hour. Cap the discussion at 5 minutes per story and move on; split or spike the rest.
- No final estimate recorded. The decision has to land somewhere durable — export to Jira, paste into Notion, or let Pokor export a CSV for the organizer.
Tooling checklist
- Hides votes until everyone has voted. Non-negotiable.
- Live-updates the participant list so you know who's in.
- Lets the organizer manage stories mid-session (things come up).
- Exports the result so it lives somewhere other than the tool.
- Works without every voter creating an account.
Pokor ticks all of these for free (core voting) and via the Organizer plan for backlog imports and exports.