Guide · 7 min read · Updated 2026-09-14
Planning Poker with a remote team
Remote estimation is not the in-person session with a video call bolted on. The cues that used to keep a room synchronised — glancing around the table, seeing someone hesitate — are gone, so the structure has to carry more of the weight.
What actually breaks remotely
- Turn-taking. Without body language, two people start at once, then nobody does. The quiet members disappear entirely.
- Simultaneity. Counting down "three, two, one, show your fingers" over a call with variable latency guarantees people see each other's answers first.
- Attention. A muted camera-off participant can be reading email for twenty minutes and nobody notices until their vote is missing.
- Shared context. In a room everyone reads the same projected story; on a call half the team is on the wrong Jira tab.
A tool that hides votes until everyone has voted, shows who has not voted yet, and puts the story text in front of every participant fixes three of those four before you change anything about how you facilitate.
A 45-minute agenda that works
- 0–3 min — Anchor. Facilitator shares the reference story and its agreed value. Everyone confirms they remember it.
- 3–5 min — Queue. Show the ordered list of stories for the session. Say how many there are, so people can pace themselves.
- 5–40 min — Rounds. Roughly four minutes per story: 60 seconds reading, 30 seconds of clarifying questions, silent vote, reveal, discuss the outliers, agree.
- 40–45 min — Close. Read back the parked items and their owners, and the agreed values.
Eight to ten stories is a realistic ceiling. Booking ninety minutes and pushing through twenty is how teams learn to hate refinement.
Facilitation habits for a call
- Name the person you want to hear from. "Marta, you voted 3 — what did you see?" beats "any thoughts?" every time.
- Announce transitions out loud. "Voting is open", "everyone has voted, revealing now" — the tool shows it, but saying it keeps distracted people with you.
- Use the participant list as an attendance check. If someone has not voted for two rounds, ask directly rather than waiting.
- Keep the discussion in one channel. Side conversations in a chat window nobody reads are how misunderstandings survive to the sprint.
Hybrid sessions: the room always wins unless you stop it
A meeting room with six people and three remote participants is the worst configuration in agile. The room talks over itself, the microphone picks up whoever sits closest, and remote voices arrive a second late — so they stop trying.
The fix is unpopular and effective: everyone joins from their own device, even the people sitting next to each other, each with their own voting card and their own audio (headphones, one open microphone in the room). Everyone becomes equally remote, and the imbalance disappears.
Distributed time zones
When the spread is more than about five hours, live estimation for the whole team is a tax somebody always pays. Two workable patterns:
- Core-hours estimation. Only stories the overlapping group can size get estimated live; the rest go to the group that owns that area.
- Rotating inconvenience. Alternate the session time so the same region is not always joining at 22:00. Announce the rotation in advance.
For genuinely asynchronous teams, keep the room open longer: participants vote as they come online, and the facilitator reveals and records once the quorum has voted, following up in writing on the outliers. It is slower, but the alternative is estimates produced by two people out of eight.
Keeping remote sessions engaging
Estimation is repetitive by nature, and a bored team votes to end the meeting rather than to describe the work. Small things help more than they should: a visible timer so people know the round is finite, reactions so agreement can be expressed without interrupting, a chat for the detail that does not need saying out loud, and a summary at the end so the hour has a visible artefact.
Planner Poker includes all of those — hidden voting with a live "who has voted" indicator, a per-round timer, reactions, room chat, an ordered task playlist, and a session summary listing every task, every vote and the agreed value.
Onboarding people who join with no account
Friction kills participation. Anyone you invite — a designer, a QA engineer, a stakeholder who joins for three stories — should be voting within seconds, not creating an account and confirming an email.
Share the room link or the six-character code; participants enter a display name and they are in. Their name is remembered for the next session, so recurring refinements need no setup at all.