What is Story Point Estimation?
Updated
Story point estimation is a collaborative technique used by agile teams to estimate the effort required to complete work items. Instead of estimating in hours or days, teams use abstract units called story points that represent the relative complexity, effort, and uncertainty of a task.
Why Story Points?
- Relative sizing - It is easier to say "this task is twice as hard as that one" than to guess exact hours
- Team calibration - Points are defined by the team, for the team, based on shared experience
- Velocity tracking - Over time, the team learns how many points they can complete in a sprint, enabling more accurate forecasting
- Reduced anchoring - Abstract units avoid the emotional baggage of time-based estimates
How Planning Poker Works
Planning Poker is a consensus-based estimation technique where team members privately select a card representing their estimate, then reveal simultaneously to avoid anchoring bias.

- A work item is presented for estimation
- Each team member privately selects a card value
- Votes are revealed simultaneously
- The team discusses discrepancies and may re-vote
- The final estimate is accepted and recorded
Scrumpy's Role
Scrumpy automates this process inside Jira. It provides:
- Multiple estimation perspectives - Estimate the same work item from different angles (complexity, time, risk)
- Live voting - See votes appear as team members submit them
- Instant feedback - Changes you make appear right away, and if something cannot be saved the previous state returns
- Automatic result computation - Configurable averaging methods calculate the final estimate
- Certainty signal - A percentage that shows how often participants settled on their votes instead of re-voting
- Variation signal - A percentage that shows how widely the vote values are spread around their average
- Required voters and reminders - Choose who must vote and nudge anyone who has not
- Asynchronous voting - Let participants vote at their own pace, with an optional deadline
- Built-in chat - Discuss estimates and react to messages during a session
- Jira integration - Accepted estimates are written directly to your Jira board or custom fields
Related articles
- Sheepherding story pointsOpen votes let the first estimate anchor the room. See how the sheep effect skews story points and how to run planning poker honestly.
- The importance of predictable velocityWhy velocity swings between sprints and how to make commitments predictable: five practical fixes for planning, capacity and dependencies.