Definition
Story Points (Estimation)
Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.
Key takeaways
- Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.
- The insight behind story points is that humans are bad at estimating absolute durations but reasonably good at relative comparison.
- Planoda supports an estimate field on every issue and rolls it into velocity and burndown, so teams can estimate in points or simply count issues — whichever suits them.
The insight behind story points is that humans are bad at estimating absolute durations but reasonably good at relative comparison. Asking 'is this bigger than that one we did last week' is easier and more reliable than asking 'how many hours will this take.' Points capture that relative size, bundling effort, complexity, and risk into one figure.
Scales are deliberately coarse — commonly 1, 2, 3, 5, 8, 13 — because the gaps between numbers grow as size grows, mirroring how uncertainty compounds for larger work. A 13 is not 'thirteen hours'; it is 'so big and uncertain that we should probably split it before committing.' That prompt to decompose is half the value of estimating at all.
Points only work within one team. They are calibrated to that team's shared sense of size, which is exactly why they feed that team's velocity but mean nothing transplanted elsewhere. Some teams skip points entirely and forecast on issue count alone, which works well when issues are kept similar in size.
Planoda supports an estimate field on every issue and rolls it into velocity and burndown, so teams can estimate in points or simply count issues — whichever suits them.
Related terms
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- BurndownA burndown chart tracks remaining work against time over a cycle, sloping from the total scope down toward zero as items are completed. It shows whether a team is on pace to finish what it committed to, making slippage visible early. The ideal line falls steadily; a flat line warns that work is stalling.
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
- BacklogA backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.