Planning Poker

Plan • Vote • Repeat

How to run a planning poker session with a remote team

A practical remote planning poker guide for facilitators who want useful estimates without dragging the meeting out.

Remote planning poker works best when the facilitator keeps the setup tiny and the discussion specific.

Before the call

Pick the stories before the meeting. Each item should have enough context for a sensible estimate: goal, acceptance criteria, known risks, and any design or technical notes the team needs.

Drop the planning poker link into Slack, Teams, or another live chat when the session starts. Session links are designed for active estimation, not long-running calendar invites or recurring meetings planned weeks ahead.

During each story

Read the story in plain language. Give the product owner or lead developer a minute to add context. Then ask for clarifying questions before anyone votes.

Once questions are answered, ask everyone to pick a card privately. Reveal together. If the scores are close, agree the estimate and move on.

When estimates split

A split is useful. It means the team does not share the same picture yet. Ask one high voter and one low voter to explain their thinking.

Keep it tight. The goal is not to win an argument. The goal is to expose hidden work, uncertainty, or assumptions. After a short discussion, vote again.

How to keep it moving

Timebox each item. If a story needs a long design debate, park it and create a follow up task. Planning poker is for estimation, not solving every technical question live.

A good remote session usually feels calm, slightly boring, and useful. That is a feature.

Remote facilitator checklist

• Share the room link before the first item
• Keep cameras optional if the team prefers it
• Read one story at a time
• Discuss only the highest and lowest estimates after a split
• Park stories that are not ready to estimate