How to play planning poker with a remote team

A good planning poker session starts before the meeting and ends with the estimates recorded in the backlog. This guide walks through the full flow for a remote or hybrid team.

Before the meeting

Pick the stories. Only bring stories the product owner can already explain, with written acceptance criteria. Estimating a poorly defined story leads to long debates and unreliable numbers.

Create the room ahead of time. In StoryPoints, create the room and paste your list of stories in the side panel, one per line. Jira links automatically become the story link.

Agree on the deck. If the team already uses Fibonacci, keep it. Switching decks mid-project makes old estimates impossible to compare.

Put the link in the meeting invite. Nobody wastes time hunting through the chat when the call starts.

During a round

1. Present the story. The product owner reads the description and acceptance criteria. Keep it to a minute or two.
2. Clear up quick questions. Objective scope questions are welcome. Technical solution debates wait until after the reveal.
3. Everyone votes silently. Each person picks a card. On screen, teammates only see that you voted, not the value.
4. Reveal. The facilitator reveals once everyone has voted. You can also turn on automatic reveal in the room settings.
5. Talk about the extremes. If there is a big gap, the highest and lowest voters explain their reasoning.
6. Vote again if needed. Use "New round" to repeat the vote for the same story.
7. Confirm the estimate. Pick the final value and StoryPoints moves on to the next story automatically.

Tips for remote teams

• Cameras on for the conversation, not the vote. While voting, attention goes to the card. During the discussion, seeing people helps.
• Use the timer for stuck stories. Two minutes of discussion is usually enough. If time runs out without agreement, the story goes back to refinement.
• Keep observers as observers. Managers and stakeholders who join as observers don't count toward automatic reveal and don't skew the result.
• Phones count. Someone on the call from a laptop can vote from their phone by scanning the invite QR code.

After the meeting

Export the CSV with the estimates and update your backlog. If you use StoryPoints with an account, the room is saved with the same link for the next sprint and your session history stays available.

Common mistakes

• Estimating in hours. Planning poker compares relative size. If the team thinks in hours, the cards lose their meaning.
• Revealing before everyone votes. Whoever hasn't voted yet is influenced by what they saw.
• Debating every 5 versus 8. Small gaps don't justify another round. Pick one and move on.
• Sessions that run too long. After an hour, estimate quality drops. Split into shorter sessions.