How to run planning poker with a remote team

Remote planning poker follows the same rules as the in-person game: everyone estimates privately, cards are revealed at once, and the team discusses differences. What changes is everything around it: people join from different rooms and time zones, attention competes with chat notifications, and quiet team members become even quieter on video. This guide covers practical ways to run online planning poker so that distributed teams get the same quality of conversation as a team around a table. If you are new to the technique itself, start with our complete guide to planning poker.

Prepare the backlog before the call

Preparation matters more remotely, because confusion is harder to resolve over video.

• Choose the stories in advance. Pick the items you want to estimate, in priority order. Eight to fifteen stories is a realistic target for an hour, depending on how refined they are.
• Write clear titles. "Add password reset by email" is better than "Reset flow". People will see the title on their own screen during voting.
• Link the details. Make sure acceptance criteria are in your backlog tool and easy to open.
• Share the list early. Sending the stories a day before gives people time to read them, so the call can focus on estimating.
• Agree on the scale and reference stories. Remind everyone which deck you are using and which completed story counts as, say, a 2. See story points explained for how to choose reference stories.

In Scrum Poker you can paste the stories into the agenda one per line, and the session steps through them in order, so nobody has to ask "which one are we on?".

Setting up the session

Screen sharing

The facilitator shares the story details (backlog item, acceptance criteria, mockups) on the video call. Voting happens in a separate tab or device, so the shared screen stays on the content being discussed.

Let people vote from their phone

Not everyone has a second monitor. Letting participants vote from their phone keeps the call and the story visible on their laptop. In Scrum Poker the facilitator gets an invite link and a QR code; people scan the code and vote from their phone without creating an account.

Spectators

Stakeholders or new team members sometimes want to observe. Give them a spectator role so they can follow the votes without being counted in the results.

Running each round

Timebox the discussion and the vote

Remote meetings drift. Set a simple structure for each story: one or two minutes to present and clarify, then a vote. A visible voting timer helps everyone commit to a card rather than waiting to see what others do. Scrum Poker offers timers of 30 seconds, 1 minute or 2 minutes.

Keep votes secret until everyone has voted

On a call it is easy for someone to say "I think it's a 3" before voting. Ask people not to share numbers out loud until the reveal. A tool that hides votes until all cards are revealed at once enforces this without the facilitator having to police it.

Discuss outliers first

After the reveal, look at the spread before the average. If most people voted 3 and one person voted 13, ask the 13 to explain first, then the lowest voter. On a remote call, invite them by name: "Sam, you went for 13, what are you seeing?" It is much easier to speak when asked directly.

Scrum Poker's results show the average, the median, how much the team agrees and who voted lowest and highest, which makes it easy to know who to ask.

Vote again, then decide

After the outliers have spoken, vote again. Usually the team converges. If not, take the higher value or agree to split the story, and move on. The facilitator keeps the estimate and the session advances to the next item.

Handling silence

Silence on a video call is ambiguous: people may be thinking, distracted or unsure how to join in. A few habits help:

• Ask open questions to specific people. "Priya, anything about the email service we should know?" works better than "Any questions?".
• Use the "?" card. Make it clear that voting "?" is a legitimate way to say "I don't understand this story yet".
• Cameras optional, voting required. Some people focus better off camera. That is fine as long as they vote.
• Watch for the same voices. If the same two people explain every outlier, rotate who you ask to summarize the story.

Keeping energy up

• Keep sessions short. Sixty minutes is a good maximum. Two shorter sessions in a week usually beat one long one.
• Take breaks. If someone plays the coffee card, take five minutes.
• Move fast on agreement. If everyone votes the same card, accept it and go to the next story. Save time for the stories that need discussion.
• Start with an easy story. A quick first estimate gets everyone voting and warms up the conversation.

Async options for distributed teams

When time zones barely overlap, a fully live session may not be practical. Some teams split the work:

• Async pre-reading: stories and questions are posted in a shared channel a day before.
• Async first pass: rough sizing of a long list with t-shirt sizes, done by each person in their own time.
• Short live session: only the stories with disagreement or open questions are discussed in a live call.

Planning poker relies on the conversation after the reveal, so keep at least a short live session for the stories that matter most.

Closing the session

Before the call ends, review what was estimated and what was skipped. Scrum Poker's session summary shows each story with its estimate and the total points, and you can copy it as text or download it as CSV to update your backlog. Note any stories that need splitting or more refinement and assign someone to follow up.

For more on choosing the right method for your team, read agile estimation techniques compared.