Free — No Account Required
Estimate Complexity,
Not Hours
Free online planning poker for agile teams. When AI agents write your code, time estimates become guesswork. Story points don’t. Share a link and start voting in seconds.
Choose your estimate
AI writes code at unpredictable speeds. That’s why you estimate complexity.
Your team uses GitHub Copilot, Cursor, Claude Code, or other AI coding agents. A feature that used to take a senior engineer 8 hours might now take 20 minutes — or 3 hours of debugging AI-generated code. Time-based estimation is broken.
Story points measure relative complexity: how many components does this touch? How uncertain is the scope? How many edge cases? These questions don’t change whether a human or an AI writes the implementation.
Planning poker with 3pts.dev gives your team a shared understanding of what’s hard and what’s not — so you can plan sprints, allocate resources, and set stakeholder expectations with confidence, regardless of how AI changes your throughput.
AI-era ready
Complexity > hours
From backlog to estimate in under 60 seconds
No accounts. No onboarding. No app to install. Just three steps and your team is estimating.
Share a Link
Create a session and paste the link into Slack, Teams, or your standup thread. Your team joins from any browser in one click.
Vote Independently
Each person picks a card. All votes stay hidden until the moderator reveals them — preventing anchoring bias and groupthink.
Align & Ship
Reveal votes, discuss the outliers, and converge on a number. Move on to the next story. Your backlog is estimated — sprint planning is done.
Why hidden votes produce better estimates
When a senior engineer says “3 points” first, everyone else gravitates toward that number. Psychologists call this anchoring bias — it silently corrupts your sprint capacity.
3pts.dev keeps every vote private until the reveal. You get each person’s genuine assessment, surface real disagreements early, and build a shared understanding of what the team is committing to.
Try it with your team
Three scales. Pick the one your team thinks in.
Fibonacci for precision. Scrum for simplicity. T-Shirt for early-stage roadmaps. Switch anytime from settings — your team’s votes carry over.
Fibonacci
The gold standard. Widening gaps mirror the growing uncertainty of larger work.
Scrum
Simplified high-end values (20, 40, 100) that teams find more intuitive at scale.
T-Shirt Sizing
Best for high-level roadmap planning when you need direction, not precision.
The moderator can switch between scales at any time from the settings panel. All three are designed around the same principle: group similar-effort work into buckets that are precise enough to plan with, abstract enough to avoid false certainty.
Used by the best engineering teams in the world
“At Atlassian, planning poker is a common practice across the company. The team will take an item from the backlog, discuss it briefly, and each member will mentally formulate an estimate.”
Dan Radigan
Atlassian
“If your scrum team is struggling to estimate the time and work required to deliver a product or feature in an agile way, why not give planning poker a try? You’ve got nothing to lose.”
Robert Drury
LogRocket
“The whole team needs to understand the logic behind the assignment of Story Points to reach a consistent practice. All team members vote — without being influenced by other team members.”
Julee Everett
Scrum.org
Frequently asked questions
What is Scrum poker and how does it work?
Scrum poker (also called planning poker) is an agile estimation technique where team members independently estimate the complexity of user stories using numbered cards. Each person votes privately, then all votes are revealed simultaneously to prevent bias. The team discusses outliers and re-votes until reaching consensus. With 3pts.dev, you run the entire process in your browser — just share a link.
Why use story points instead of hours?
Story points measure relative complexity, not duration. This is especially critical now that AI coding agents (GitHub Copilot, Cursor, Claude Code) handle implementation at wildly unpredictable speeds. A feature that takes a senior engineer 8 hours might take an AI 20 minutes — or 3 hours of debugging. Story points capture what actually matters for planning: how complex is this work relative to other work the team has done?
Why are Fibonacci numbers used in agile estimation?
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21…) works because the gaps between numbers grow as the values increase — reflecting the reality that larger tasks are harder to estimate precisely. You can confidently say a story is a 3 versus a 5, but distinguishing a 34 from a 40 is meaningless. The growing gaps force teams to bucket similar items together rather than argue over false precision.
How does AI-assisted development change estimation?
AI agents make time-based estimation unreliable because identical tasks can vary wildly in duration depending on AI performance, prompt quality, and code context. But relative complexity doesn’t change — a story that touches 5 services and handles 3 edge cases is still more complex than one that updates a single field, regardless of who (or what) implements it. Teams using AI agents should estimate complexity, not hours. Story points are the right abstraction.
Is 3pts.dev really free?
Yes. 3pts.dev is free to use — no sign-up, no email, no credit card. Create a room, share the link, and start estimating immediately.
How is 3pts.dev different from other planning poker tools?
Most planning poker tools require accounts, have free-tier limits, or bury useful features behind paywalls. 3pts.dev is different: zero friction. Open the link, pick a name, start voting. All features are free. SSL encrypted. Votes stay hidden until reveal. The moderator controls the session. It works exactly the way planning poker should — without the overhead.
Your next sprint planning starts here
No accounts. No credit cards. No onboarding. Share a link with your team and you’re estimating in under 10 seconds.
Launch a Free Session