When to Assign Zero Story Points

When to Assign Zero Story Points

The Fibonacci scale starts at 0, but when should you actually use it? Zero-point stories are a controversial but practical tool in agile estimation.

What Qualifies as Zero Points

A zero-point story represents work that is so trivial it has effectively no complexity, risk, or uncertainty:

• Fixing a typo in the UI
• Updating a config value (e.g., changing an API URL)
• Toggling a feature flag
• Minor copy changes
• Adding an existing component to a new page (no logic)

The key test: "Can any team member complete this in under 30 minutes with zero risk of regression?" If yes, zero is appropriate.

The Arguments

For zero-point stories:

• They still need to be tracked in the backlog (they are real work).
• Assigning 1 point inflates velocity with meaningless work.
• They do not affect sprint capacity in any meaningful way.

Against zero-point stories:

• Every piece of work has some non-zero effort, even if minimal.
• Some teams use a minimum of 1 point for all tracked work.
• Zero-point stories are invisible in velocity calculations.

Practical Approach

Most mature teams settle on this convention:

Effort < 15 minutes, zero risk  → 0 points (or skip estimation entirely)
Effort 15-60 minutes, low risk  → 1 point
Effort 1-4 hours, moderate risk → 2-3 points

Impact on Velocity

Zero-point stories do not affect velocity math. If your team completes 5 stories worth 0, 1, 3, 5, 8, the sprint velocity is 17, not "17 across 5 stories." The zeros are invisible but still tracked as completed work.

Alternative: Sub-Tasks

Instead of creating zero-point stories, some teams add trivial items as sub-tasks under an existing story. This keeps them visible without cluttering the estimation process.

Story: "Update user settings page" (5 pts)
  Sub-task: Fix typo in header
  Sub-task: Update copyright year in footer
  Sub-task: Implement new settings form (main work)

Choose the approach that works for your team. The important thing is consistency.