Professional agile estimation for remote teams. Run planning poker sessions with Fibonacci sequences, T-shirt sizing, and custom scales. Perfect for sprint planning and backlog refinement.
No registration required. Create a session in seconds and share the link with your team. Perfect for quick estimation sessions.
Built for distributed teams. Real-time sync ensures everyone sees votes simultaneously, no matter where they are.
Automatic calculation of average, median, min, and max estimates to help your team reach consensus quickly.
Planning Poker, also known as Scrum Poker, is a consensus-based technique for estimating effort or relative size of development goals in software development. It was first described by James Grenning in 2002 and later popularized by Mike Cohn in his book "Agile Estimating and Planning".
The technique combines expert opinion, analogy, and disaggregation into an effective approach for estimating. Team members make estimates by playing numbered cards face-down to avoid bias, revealing them simultaneously to discuss differences and reach consensus.
The Fibonacci sequence (0, 1, 2, 3, 5, 8, 13, 21, 34, 55...) is commonly used in Planning Poker because it reflects the inherent uncertainty in estimating larger items. As numbers get bigger, the gaps increase, which mirrors how our confidence in estimates decreases for larger, more complex work.
"Team members consistently give very different estimates for the same stories."
Solution: This often indicates unclear requirements or different understanding of the work. Use the discussion phase to clarify assumptions, break down complex stories, and ensure everyone has the same understanding of the acceptance criteria.
"One or two team members always influence the final estimates."
Solution: Emphasize simultaneous card revelation, encourage quieter team members to speak first during discussions, and consider using anonymous digital tools for initial rounds of sensitive estimates.
"Discussions go on too long without reaching consensus."
Solution: Set strict time limits (5-10 minutes per story), use techniques like "fist of five" for quick consensus checks, and remember that estimates can be refined later as you learn more.
Use XS, S, M, L, XL for high-level estimation when precision isn't critical.
Sort stories into pre-defined buckets (1, 2, 3, 5, 8, 13, 20) for faster estimation of many items.
Team members place dots on a scale to estimate story complexity quickly.
Organizations that implement Planning Poker typically see significant improvements in project predictability and team collaboration.
While in-person Planning Poker with physical cards is ideal, remote teams need digital solutions. Here's what to look for in a planning poker tool:
| Feature | Essential | Nice to Have | Why It Matters |
|---|---|---|---|
| Real-time Synchronization | ✓ | All participants see votes simultaneously | |
| Custom Card Sets | ✓ | Support for Fibonacci, T-shirt sizes, custom scales | |
| No Registration Required | ✓ | Quick setup for ad-hoc sessions | |
| Results Analytics | ✓ | Average, median, consensus metrics | |
| Story Context | ✓ | Ability to add story titles and descriptions |
Our tool provides all the essential features above, with no registration required. Perfect for both remote and hybrid teams.
Starting a session is simple: click "Create Session", enter your name, choose an avatar, and you'll get a unique session link. Share this link with your team members so they can join. No registration or setup required.
Pro tip: Send the session link via Slack, Teams, or email before your meeting starts so everyone can join quickly.
Our tool uses the Fibonacci sequence (1, 2, 3, 5, 8, 13, 20, 40, 100) plus special cards:
The ideal size is 3-9 team members. Fewer than 3 people doesn't provide enough diverse perspectives, while more than 9 makes it difficult to manage discussions and reach consensus.
Include: Developers, testers, product owners, and anyone who will work on the stories. Each person brings valuable insights about different aspects of implementation.
For sprint planning: 1-2 hours for a 2-week sprint. Estimate 2-5 minutes per story on average. Some complex stories may take longer to discuss, while simple ones can be estimated quickly.
Don't worry! Disagreement often reveals important information. Here's how to handle it:
Absolutely! This tool was designed specifically for remote and distributed teams. Features that help remote teams:
Best practice: Use alongside video conferencing (Zoom, Teams) for discussion while using our tool for voting.
After revealing votes, you'll see four key statistics:
Which to use? Most teams use the median for final story points, as it's less influenced by extreme estimates.
Your privacy is important to us:
Sessions are designed to be temporary - perfect for focused estimation meetings without long-term data storage.
"Moving to digital Planning Poker reduced our sprint planning time by 40% while improving estimate accuracy. The real-time sync across global teams was a game-changer."
Results: Reduced planning time from 4 hours to 2.4 hours per sprint, improved sprint commitment accuracy by 25%, enabled seamless collaboration across 4 time zones.
"As we scaled rapidly, Planning Poker helped us maintain consistent estimation practices across new team members. No training needed - people get it immediately."
Results: Onboarded 15 new developers with consistent estimation practices, maintained team velocity during 300% growth period, improved cross-team story point calibration.
"The transparency and collaboration in Planning Poker sessions improved our stakeholder confidence. They can see the estimation process and understand the reasoning."
Results: Increased stakeholder buy-in for project timelines, reduced scope creep by 35% through better story definition, improved budget predictability for annual planning.
Pro tip: Start with a simple story everyone understands to establish your baseline. This helps calibrate estimates for more complex work.