Story Point Estimator
Your data never leaves your browserAnalyse a story or task description and suggest a Fibonacci story point estimate with reasoning.
Brie — Bug Reporting Tool
Found a bug while testing?
Brie captures screenshots, console logs, network data, and session replays in one click — so developers get the full context without the back-and-forth.
About Story Point Estimator
Paste a description of a user story or development task and receive a suggested story point estimate on the Fibonacci scale (1, 2, 3, 5, 8, 13, 21). The tool analyses the text for signals of technical complexity, unknowns, dependencies, and scope to produce a breakdown and an explained estimate. Useful as a starting point for planning poker sessions or when you need a quick reference estimate.
How to use
- Paste a description of the task or user story into the input panel.
- Click Convert to analyse the description.
- Review the complexity breakdown and suggested Fibonacci story points with reasoning in the output.
More Product Owner Tools
Sprint Velocity Calculator
Calculate average sprint velocity, median, standard deviation, and suggested capacity for planning.
User Story Formatter
Format user stories in the standard "As a… I want… so that…" structure with auto-generated acceptance criteria.
RICE Score Calculator
Calculate and rank features by RICE score (Reach × Impact × Confidence / Effort).
Frequently Asked Questions
FAQs about Story Point Estimator
What are story points?
Story points are a unit of measure for expressing the overall effort required to fully implement a user story. They account for complexity, uncertainty, and the amount of work involved — not just time.
Why use the Fibonacci sequence for story points?
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21…) naturally reflects increasing uncertainty. As stories get larger, the gaps between values grow, acknowledging that precise estimation of large work is difficult.
Is this tool a replacement for planning poker?
No. It is a starting reference. Planning poker with your whole team captures tacit knowledge, surfaces disagreements, and builds shared understanding that no tool can fully replicate.
What signals does the estimator look for?
The estimator analyses word count, technical keywords (OAuth, integration, migration, refactor, etc.), scope indicators (multiple, all, entire), and dependency language (depends on, requires, blocked by) to gauge complexity.
Does this tool store my data?
No. All analysis happens in your browser. Nothing is sent to any server.