Estimate user stories with your distributed agile team in real time. Create a free room, share the link, and start your sprint planning session from anywhere in the world.
Planning poker is an agile estimation technique where every team member privately votes on task complexity, then everyone reveals their card simultaneously. That simultaneous reveal is the whole point: it eliminates anchoring bias — the cognitive phenomenon where the first number someone hears unconsciously pulls everyone else toward it.
For remote teams, this mechanic is even more important than in a physical room. In a video call without a structured process, whoever speaks first anchors the entire discussion. Online planning poker enforces the rule automatically: the tool holds all votes until every participant has submitted, then reveals them all at once.
Remote teams at companies including Google, Netflix, and Amazon use planning poker for this reason: it surfaces disagreement early, gives quieter team members an equal voice, and produces estimates the whole team owns.
Running planning poker online with a distributed team takes less than 30 seconds to set up.
Go to planning-poker-free.com, click Create Room, and choose your estimation scale. No account, no email, no credit card. You get a unique room link immediately.
Paste the room URL into Slack, Teams, or your calendar invite. Participants click the link, enter a display name, and join — nothing to install, no login wall.
Give the team at least 24–48 hours of advance access to the stories so they arrive informed rather than reading for the first time during the session.
The facilitator presents each story, answers clarifying questions, then opens voting. Every participant selects a card in secret. When all votes are in, the tool reveals them simultaneously. If estimates converge (within one Fibonacci step), record the consensus and move on.
If there's a spread — say a 3 and a 13 in the same round — ask the outliers to explain their reasoning. These moments surface hidden complexity and are among the most valuable parts of the session.
Limit each session to 10–15 stories to avoid estimation fatigue. If a story won't converge after two rounds, accept the higher estimate or mark it for refinement.
The biggest enemy of a smooth remote planning session is friction. See the difference in join experience:
This matters even more for remote and distributed teams where contractors and external stakeholders can join without giving you their email or creating yet another account.
The card deck your team uses shapes how conversations unfold.
| Scale | Values | Best for |
|---|---|---|
| Fibonacci ✓ | 1,2,3,5,8,13,21,34,? | Most teams — recommended for all new teams |
| Modified Fibonacci | 0,½,1,2,3,5,8,13,20,40,100 | Mature teams splitting stories finely |
| T-Shirt Sizes | XS,S,M,L,XL,XXL | High-level backlog grooming, stakeholders |
| Powers of 2 | 1,2,4,8,16,32 | Engineering-heavy teams |
For most remote scrum teams, start with Fibonacci. Change your scale only when the team consistently finds it doesn't reflect how they think about work.
Answer 6 questions about your current estimation process:
| Method | Anchoring bias? | Remote-friendly? | Async support? | Setup time |
|---|---|---|---|---|
| Planning Poker ✓ | ✓ Prevented | ✓ Designed for it | ✓ Yes | Under 1 min |
| Fist-of-five voting | ✗ Visible hands | ~ Partial | ✗ No | Instant |
| Spreadsheet sizing | ✗ Sequential rows | ~ Partial | ~ Sort of | 5–10 min setup |
| Affinity estimation | ✓ Silent grouping | ✗ Hard to replicate | ✗ No | 10+ min |
| Manager assigns estimate | ✗ Complete anchor | ~ N/A | ✓ Yes | Instant |
Connect your distributed team for sprint planning right now. Works in any browser, from any timezone.
Create Free Room →