How to run planning poker with a remote team
By Thimira Dulakshitha Kularatne · Updated
Remote and hybrid teams can’t pass physical cards around, but planning poker works just as well online, and sometimes better, because nobody can see anyone else’s card before the reveal. This guide covers preparation, running each round on a call, and the habits that keep a remote estimation session short and useful.
Before the session
- Refine the backlog first. Stories should have a clear goal and acceptance criteria before they reach the table.
- Pick 8 to 15 stories for an hour. More than that and attention drops, especially on a call.
- Paste the list into the job board (one story per line) so everyone sees what’s coming.
- Choose the deck in advance. Stick with the one your team already knows.
- Send the room link in the calendar invite, so people join straight from the meeting.
Running each round on a call
Share the story, not your screen
Put the story on the mat so it shows for everyone, including people on phones. Keep screen sharing for when you need to show a design or some code.
Take questions, then vote
Give the team a minute to ask about scope. Once the questions dry up, everyone plays a card. Cards stay hidden, so nobody anchors on the first voice.
Reveal when everyone is in
Wait until every seat shows a card. If someone is quiet for too long, a gentle nudge beats calling them out on camera.
Discuss the outliers
Ask the highest and lowest voters to explain, in that order. Keep it short: a two-minute timer stops one story taking over.
Lock it in and move on
Agree on a number, lock it in on the job board, and pull up the next story. Re-vote only after a real change in understanding.
Who does what
- Facilitator (often the Scrum Master): runs the pace, reveals cards, starts re-votes and locks in estimates.
- Product Owner: explains the story and answers scope questions. Usually joins as an observer, so their opinion doesn’t steer the vote.
- Developers and testers: everyone who’ll build or test the work plays a card.
Remote pitfalls, and how to avoid them
- Cameras-off silence. Remote teammates are less likely to interrupt. Invite the quiet people by name when their card is an outlier.
- Voting before reading. People skim on calls. Read the story aloud, or give 30 seconds to read it, before anyone plays a card.
- Time zones. For teams spread across time zones, keep sessions short and frequent, or skip the meeting: collect votes async so everyone estimates in their own hours, then meet only for the stories where the cards disagree.
- Losing the results. Export the estimates at the end, as CSV or a Markdown table for your tracker, so nothing gets retyped from memory.
What to look for in an online planning poker tool
- No sign-up for teammates. A link and a name should be enough.
- Cards hidden on the server until the reveal, not just blurred in the browser.
- Works on phones, for people joining from a train or a second screen.
- A story queue, a shared timer and an export, so the facilitator isn’t juggling tabs.
- Control over who can reveal and who can join the room.
Benchmark does all of this for free. If your team is still picking a scale, read Fibonacci story points explained.
Run your next session here
Open a room, paste your stories into the job board, and send the link. Your team can join from any device in seconds.