What Are Story Points?
Story points are a unit of relative complexity used in agile estimation. This guide explains how they work and how to estimate with them.
Definition of Story Points
Story points represent the relative size, complexity, and effort of a user story or backlog item. They're abstract—a "5" isn't five hours. It means the item is roughly five times as complex as your baseline "1". Teams define their own scale and reference stories.
Why Story Points Instead of Hours?
Hours vary by person and context. Story points focus on relative size—everyone can agree that item A is bigger than B without committing to exact time. That makes estimation faster and less contentious. Velocity (points per sprint) becomes a stable planning metric.
Common Story Point Scales
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) is popular—gaps grow as size increases, which reflects uncertainty. Some teams use T-shirt sizes (S, M, L) or powers of two. Consistency matters more than the exact scale. Our story point poker tooluses Fibonacci by default.
Estimating with Planning Poker
Planning poker is the standard way to assign story points. Each team member votes with a card. Votes are revealed together to avoid anchoring. Differences spark discussion. The team repeats until consensus. Try our free online planning poker.
Sprint Estimation and Velocity
Once stories have points, you can sum them for a sprint. Velocity = points completed per sprint. Over time, velocity stabilizes and you can forecast how much the team can deliver. For best practices, see our agile estimation guide.