Skip to content
Ever Works

Agile Story Points & Velocity

A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.

Visit Website
Agile Estimation Scrum

Last updated: 2026-03-10 12:21

Overview

Story points are a relative estimation method in Agile that helps teams assess effort, complexity, and risk for backlog items. Unlike time-based estimates (hours or days), story points represent relative complexity, effort, and risk.

What Are Story Points?

Story points consider:

Story points do NOT equal hours. A 5-point story isn't "5 hours of work."

Why Use Story Points Instead of Hours?

Benefits of Story Points:

  1. Team Collaboration: Encourages team discussion and consensus
  2. Reduced Bias: Less emotional attachment than hourly estimates
  3. Better Forecasting: Improves accuracy over time
  4. Accounts for Uncertainty: Better for complex, uncertain work
  5. Focuses on Value: Emphasizes what's being delivered, not just time spent

Researchers have found that this improves estimate accuracy, especially on items with a lot of uncertainty as we find on most software projects.

The Fibonacci Sequence

Story points typically use a modified Fibonacci sequence: 1, 2, 3, 5, 8, 13, 20, 40, 100

Why Fibonacci?

Scale Interpretation:

Planning Poker

Planning Poker® is a consensus-based technique for agile estimating.

How It Works:

  1. Present Item: Team discusses a user story from the backlog
  2. Brief Discussion: Clarify questions, discuss approach
  3. Private Estimation: Each member mentally formulates an estimate
  4. Simultaneous Reveal: Everyone holds up a card with their estimate
  5. Discuss Differences: If estimates vary, discuss reasoning
  6. Re-estimate: Repeat until consensus is reached

Planning Poker Cards:

Cards display values like: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, ?, ∞

Special cards:

Why Planning Poker Works:

Velocity

Velocity is a metric that measures the amount of work a team can complete during a single sprint or iteration.

Calculating Velocity:

Velocity = Sum of story points of all completed user stories in a sprint

Example:

Using Velocity for Planning:

Once you know your velocity:

Velocity Rules:

  1. Only Count Completed Work: Partially done doesn't count
  2. Use Team-Specific Velocity: Don't compare across teams
  3. Wait 3-5 Sprints: Velocity stabilizes after a few sprints
  4. Account for Variations: Use average, not just last sprint
  5. Velocity is a Guide: Not a commitment or performance metric

Implementation Steps

Step 1: Establish a Baseline

Pick a reference story that the whole team understands. Assign it a number (often 3 or 5). Estimate other stories relative to this baseline.

Step 2: Estimate as a Team

Use Planning Poker or similar technique. Ensure whole team participates.

Step 3: Track Actuals

Record which stories were completed each sprint and their point values.

Step 4: Calculate Velocity

After 3-5 sprints, calculate average velocity.

Step 5: Use for Planning

Plan future sprints based on your established velocity.

Step 6: Refine Over Time

Adjust estimates based on what you learn. Velocity should stabilize and become more predictable.

Common Pitfalls

1. Treating Points as Hours

Story points are NOT time. Don't convert them to hours.

2. Comparing Team Velocities

One team's 50 points ≠ another team's 50 points. Story points are team-specific.

3. Using Velocity as Performance Metric

Velocity is for planning, not judging team performance. Pressuring teams to increase velocity leads to point inflation.

4. Estimating Too Precisely

Don't argue whether something is 7 vs. 8 points. Use Fibonacci gaps to avoid false precision.

5. Incomplete Stories

Only completed stories count toward velocity. Don't count partially done work.

6. Changing Point Values After Sprint Starts

Once sprint starts, don't re-estimate. Learn for next time.

Benefits

Best Practices

Estimating:

Tracking Velocity:

Planning:

Tools Supporting Story Points

Integration with Time Tracking

While story points avoid time estimates:

Who Benefits Most

Related Concepts

Related Items

1-3-9 Method

A powerful task prioritization framework that limits daily focus to 13 manageable tasks: one critical priority, three important tasks, and nine smaller tasks to ensure proper attention allocation across different priority levels.

10-10-10 Rule

Decision-making framework by Suzy Welch that evaluates choices by considering their impact in 10 minutes, 10 months, and 10 years. This method enables logical, grounded decisions by balancing short-term demands with long-term vision, eradicating rash decision-making.

12 Week Year Method

A productivity and goal-setting system developed by Brian P. Moran and Michael Lennington that redefines your year to be 12 weeks long, eliminating procrastination through increased urgency and shortened planning cycles to achieve more in less time.

18-Minute Plan

The 18-Minute Plan is a daily productivity ritual created by Peter Bregman consisting of 5 minutes of morning planning, 1 minute of refocus every hour for 8 hours, and 5 minutes of evening review to manage your day and master distraction.