Run Planning Poker sessions with your agile team instantly. No account, no download, no cost — just create a room, share the link, and start estimating story points together.
An agile estimation tool helps scrum and agile teams assign relative effort values — called story points — to user stories or backlog items before a sprint. The most widely used format is Planning Poker, a consensus-based technique where each team member privately selects a card value and all cards are revealed simultaneously.
This prevents anchoring bias: no one sees someone else's estimate before committing to their own. Research consistently shows that teams using planning poker produce more accurate estimates than those using ad-hoc verbal estimates, because simultaneous reveal forces independent thinking and surfaces hidden assumptions.
Create a free room, share the link with your team. No accounts needed for anyone.
Every participant picks a card in secret. The tool shows who voted but hides the values.
All cards flip simultaneously. Outliers discuss, re-vote if needed, and consensus is reached.
Visit planning-poker-free.com and click "Create Room". Choose your estimation scale and get a unique room link immediately — no account or email needed.
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.
The PO presents each story from the backlog. Team members ask clarifying questions to surface assumptions, dependencies, and risks before voting begins.
Each participant selects a Fibonacci card — 1, 2, 3, 5, 8, 13, 21 — representing their effort estimate. The tool shows who has voted but hides what they voted.
The facilitator triggers the reveal. If estimates converge, that number becomes the story point estimate. If there's a wide spread, outliers explain their reasoning.
A second round after brief discussion usually produces consensus. Repeat for every story in the backlog. A full 10–15 story session runs 45–90 minutes.
Special cards in every deck: ? (I need more information before I can estimate) and ☕ (I need a break). Both are practical signals that improve session quality.
Not every team uses the same estimation scale. Choose the one that fits your workflow:
Values 1, 2, 3, 5, 8, 13, 21. Reflects the natural uncertainty of software work — larger tasks have wider error bands. Recommended for teams new to story points.
Adds 0, 0.5, 20, 40, 100 and special cards. The 0 card is used for trivial tasks; 100 flags an epic that must be broken down before estimating.
XS, S, M, L, XL, XXL. Better for non-technical stakeholders and early-stage product discovery. Intuitive and fast, but harder to aggregate into velocity charts.
1, 2, 4, 8, 16, 32. Preferred by engineering teams for its logarithmic clarity. Each card is exactly double the previous value.
Advanced teams build custom scales tied to days, risk levels, or domain-specific units. Enter any values your team uses.
Every deck includes "?" (uncertainty — story needs clarification) and the coffee cup (break needed). Both signals improve session quality.
Remote-first agile teams face a specific challenge: without a physical table of cards, estimation sessions collapse into "what does everyone think?" — which immediately introduces anchoring bias. An online planning poker tool solves this structurally.
Simultaneous card reveal — All votes are hidden until every participant has selected a card. This mirrors the in-person experience and prevents early anchors from forming.
Shareable room link — One URL is all a team member needs to join. No account creation, no app install. Works on any browser, including mobile.
Unlimited participants — No artificial cap on room size. Whether your team has 4 developers or 20, everyone can vote simultaneously.
Async support — For teams across time zones, members can vote on their own schedule. The facilitator reveals and discusses in the next sync meeting.
Many planning poker tools start free but gate core features behind a paywall: vote history, unlimited stories per session, custom decks, or rooms with more than 5 participants. This creates friction at the worst possible moment — mid-sprint planning.
| Feature | planning-poker-free.com | Most competitors (free tier) |
|---|---|---|
| No registration required | ✓ Anyone joins instantly | ✗ Account required |
| Unlimited participants | ✓ No cap | ✗ 5–9 participants max |
| Custom card decks | ✓ Free | ✗ Premium only |
| Unlimited voting rounds | ✓ No limit | ✗ Often capped |
| Mobile-responsive | ✓ Full support | ~ Varies by tool |
| No ads during session | ✓ Clean interface | ~ Ads common on free tier |
| Jira/Linear integration | ✗ Not needed for core flow | ✓ On paid plans |
For teams that need Jira integration or persistent room IDs, other tools exist. But for the core planning poker workflow — and most teams need nothing more — free is enough.
INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable. If a story can't be estimated, it likely lacks clear acceptance criteria.
When estimates diverge, set a two-minute timer for the highest and lowest voters to explain their reasoning before re-voting. Without a timebox, estimation sessions drift.
The PO's role is to clarify requirements, not to anchor the team's effort estimate. Most planning poker tools let the facilitator mark a participant as "observer".
In your first few sprints, select 2–3 completed stories as "reference stories" — a 1, a 5, and a 13. When estimating new stories, the team compares against these anchors.
Story points are relative, not hours. A team's sprint velocity becomes a reliable planning tool after 3–5 sprints, regardless of absolute numbers.
If a story's acceptance criteria change after estimation, re-run the card vote. Stale estimates are worse than no estimates.
Start estimating story points with your agile team right now. No credit card, no email, no friction.
Create Free Room →