Remote planning poker: how to estimate with a distributed team

Remote planning poker works the same way as planning poker round a table: everyone chooses an estimate in private, the votes are revealed at the same moment, and the team talks through the differences before agreeing a number. What changes is everything around the cards. You need an online room that keeps votes hidden until the reveal, a call where people can hear each other and see the item, and a facilitator who works a little harder to bring in the voices a meeting room would pick up naturally.

The short version: one link for everyone, the item and its acceptance criteria on screen, hidden votes, outliers speak first, a timer on every discussion and a clear decision before you move on. The rest of this guide covers the details and ends with an agenda you can paste into your next calendar invite.

What changes when planning poker goes remote?

The mechanics survive the move online almost untouched, and some even improve. Round a table, people can see who is reaching for the 13 before anyone reveals; a good online tool shows nothing until the reveal. Everyone reads the same wording of the item.

The conversation is what gets harder. Mike Cohn’s Mountain Goat Software notes that remote estimation suffers when people multitask, or when one person pushes a number before others have thought for themselves. Add audio lag, people talking over each other and the missing small cues, such as a frown when someone calls a change “just config”, and it’s easy to see why remote sessions drift.

Set up the room before anyone joins

Most of the minutes lost in a remote session go in the first five: hunting for the link, sharing the wrong screen, discovering that half the items have no acceptance criteria. A little preparation removes all of it.

• One planning poker room with hidden votes. Use a tool that keeps every vote hidden until the reveal, then shows the whole team’s cards at once. Our guide to choosing a planning poker tool covers the other features worth checking.
• The items, ready to read. Load the 8 to 10 items you plan to estimate, in priority order, each with a short description and acceptance criteria. If people have to open another tab to read an item, some of them won’t.
• Both links in the invite. Put the call link and the room link in the calendar invite, so nobody has to ask for them.
• The deck and the yardsticks. Use the deck the team always uses and keep two or three reference stories handy, so people can say “bigger than the CSV export, smaller than the login work”.
• A home for notes. Agree where questions, assumptions and follow-ups go, ideally on the item itself. Decisions made on a call are easy to lose once it ends.

Tip Ask the product owner to reread the items the day before and fix anything a newcomer couldn’t follow without asking. Vague items cost more remotely, because every clarifying question takes longer to ask and to answer.

On planningpoker.org Anyone can start a free guest session without an account and share a link; guests join with just a name. Guest sessions hold up to 8 people and are deleted after 24 hours. Votes stay hidden until the reveal, and nobody’s vote is sent to anyone else’s browser before then.

Video etiquette for estimation calls

Agree a few norms once and write them into the team’s working agreement. These make a sensible starting point.

• Cameras on for discussion, by agreement. Faces help when the team is talking through a split vote, because you can see who wants to come in. They aren’t needed while people read and vote, and nobody should feel pressed to stay on camera all day.
• Hide self-view. Stanford researcher Jeremy Bailenson has argued that video calls are tiring partly because of close-up eye contact, the extra effort of sending and reading cues on screen, watching your own image all day and being stuck in front of a camera. He suggests hiding the self-view window and making some calls audio-only. His points are arguments rather than tested findings, but the fixes cost nothing.
• Unmuted in a small, quiet group. With five or six people in quiet rooms, staying unmuted keeps the conversation natural and makes it easier to jump in. Mute when there is background noise, and use raised hands once the group grows.
• No numbers before the reveal. Nobody says “surely this is a 2” until the votes are in, and that includes the product owner, whose sense of size carries extra weight. A number said aloud becomes an anchor: in Amos Tversky and Daniel Kahneman’s classic experiment, a number from a rigged wheel of fortune pulled people’s estimates towards it.

Time zones: find the overlap, then protect it

When a team spans time zones, the scarce resource is the window when everyone is awake and working. Spend it on the conversations that need everyone. Planning poker earns a place in that window because its value is in the discussion; status updates don’t.

Take a team split between Manchester and Pune. In the British summer, 09:00 to 12:30 in Manchester is 13:30 to 17:00 in Pune, a comfortable overlap. When UK clocks go back on the last Sunday in October, the same Manchester slot becomes 14:30 to 18:00 in Pune, because India doesn’t change its clocks. Check recurring invites whenever the clocks change.

When there is barely any overlap, for example between San Francisco and Bengaluru, don’t leave one group estimating at 7am for ever. Try these instead:

• Rotate the inconvenience. Alternate the slot so early starts and late finishes are shared.
• Go shorter and more often. Two 30-minute sessions a week fit an awkward overlap better than one 90-minute marathon.
• Vote async, discuss live. Let people vote on their own time and use the shared slot only for the items where the votes disagree. Our guide to async planning poker shows how to set this up.
• Record decisions, not meetings. Someone who missed the call needs the agreed estimate and the reason for it, not a 45-minute recording. Two lines on the item will do.

How to keep quieter people in the conversation

Hidden votes give everyone an equal say in the number. They don’t guarantee an equal say in the discussion that follows, and video calls tend to favour whoever unmutes fastest. Three habits fix most of it.

Ask the outliers first, by name

After the reveal, invite the highest and lowest voters to speak first, by name, with an easy way out: “Aisha, you went 8. What are you seeing?” It turns the outlier from someone who might be wrong into someone with information the team needs. Mountain Goat Software recommends the same order for remote teams.

Use a written round for divisive items

When an item splits the team, give everyone 60 seconds to type one sentence in the chat before anyone speaks: the riskiest part, or the assumption behind their vote. Then read them out. People who think before they talk, or who work in a second language, get the same airtime as the quickest talker.

Notice who hasn’t spoken

Keep a mental tally. If someone has been silent for three items, ask them directly about the next one, or check in privately afterwards. Silence sometimes means agreement and sometimes means the person stopped following ten minutes ago. Make it safe to be unsure, too: a “?” card or “I don’t know this area” is useful information, not a confession.

Here is how it plays out. A grocery delivery team is estimating “Let customers reschedule a delivery from the tracking page”. The votes are 3, 3, 5, 5 and 13. The 13 belongs to Tomás, a tester who joined last month and rarely speaks first. Asked directly, he explains that the courier’s system won’t accept changes once a van has left the depot, so the page needs a second path for those orders. The team splits the story: rescheduling before dispatch is a 3, and the out-for-delivery case becomes its own item. Without the prompt, the 3s would have carried the call.

Timebox every round

Attention runs out faster on a call than in a room. Keep sessions to 45 or 60 minutes, and if you need longer, take a proper break rather than pushing on. Within the session, give every item the same shape:

1. Present, in a minute. The product owner summarises the item and its acceptance criteria without hinting at a size.
2. Questions, for two minutes. Clarifying questions only. If a question opens a design debate, the item probably isn’t ready.
3. Vote and reveal. Everyone votes; the moderator reveals once all the votes are in.
4. Discuss, for three minutes. Outliers first, then anyone with new information.
5. Decide or park. If the votes have converged, agree the number. If they are still far apart after a second round, park the item.

Use a visible timer so nobody has to be the clock. When it runs out, the facilitator asks one question: “Do we need more time, or more information?” More information means the item goes to a parking lot with an owner and a next step: a spike, a question for a specialist or a split into smaller stories.

At around four minutes an item, a 45-minute session gets through eight to ten items once you allow for the start and the wrap-up. If your team regularly manages three, the items probably need more refinement before they reach estimation.

Hybrid meetings: when some of the team share a room

Hybrid sessions are the hardest format. Four people round a meeting-room table and three on a screen quickly turn into a meeting and its audience. The room talks, laughs and glances at each other, while the remote people wait for a gap that never comes.

The fix is to run the session as if everyone were remote:

• Everyone votes on their own device. No physical cards in the room. If the room holds up cards while remote people use a tool, the room sees each other’s cards and the remote people don’t.
• Everyone joins the call. People in the room join on their laptops with microphones muted and speakers off, so their faces, chat and raised hands appear like everyone else’s. One good room microphone carries the sound.
• Remote people speak first. When the facilitator asks for views after the reveal, start with the people on the call.
• A remote advocate. If the facilitator is in the room, ask someone else there to watch the chat and the raised hands on the call.
• No side conversations. A quick word across the table is invisible to the call. If it’s worth saying, say it to everyone.

A remote planning poker agenda you can copy

This agenda fits a 45-minute session for a team of five to eight. Adjust the number of items to your pace, not the other way round.

1. The day before. The product owner shares the 8 to 10 items at the top of the backlog, each with acceptance criteria. The facilitator creates the room, adds the items and puts both links in the invite.
2. 0:00 to 0:05, check in. Confirm the goal (“size the top eight for sprint 24”), the deck and the reference stories, and remind everyone: no numbers before the reveal.
3. 0:05 to 0:38, estimate. For each item: present, questions, vote, reveal, outliers first, decide. Park anything that hasn’t converged after two rounds.
4. 0:38 to 0:43, clear the parking lot. Give every parked item an owner and a next step, such as a question for a customer, a spike or a split.
5. 0:43 to 0:45, read back. Read out the agreed estimates, check they’re recorded where the team plans, and say what will be voted on async before the next session.

The grocery team’s session ended with this list:

For more on running the discussion itself, see our planning poker facilitation tips. If your team is new to the format, start with how to run a planning poker session.