Story Points Remaining
Story Points Remaining measures the total number of story points that are not yet completed at a specific point in time.
It represents the remaining workload based on the current story point values of work items that have not reached the Completed lifecycle state.
This Metric focuses on scope and capacity, not delivery speed, flow efficiency, or time spent.

What Question Does Story Points Remaining Answer?
Story Points Remaining is designed to answer:
How much estimated work is still left to complete?
How Story Points Are Counted
Story Points Remaining is a snapshot-based Metric. At each evaluation point, story points are summed from all work items that are not in a Completed lifecycle state, using the current value of the Story Points field. Without a Time dimension, the Metric reflects the remaining story points at the current moment.
When a Time dimension is applied, the value is recalculated independently for each time period. Time represents the state of remaining work at each point, not when work was created or completed.
Configuration
Story Points Remaining has no options of its own. Like every Metric it can be given a Metric Name and a Description — see Metric Configuration.
What You Can Analyse with Story Points Remaining
Story Points Remaining is commonly used to analyse:
Remaining Scope
- How much work is still left to complete
- Current backlog, sprint, or release scope
Scope Trends
- Whether remaining work is increasing or decreasing over time
- Visibility into scope changes during a sprint or release
Burn-Down and Progress
- Whether work is being reduced at a steady pace
- Comparison of planned versus remaining effort
Capacity Risk
- High remaining points late in a sprint or release
- Early signals that planned timelines may be at risk
Workload Distribution
- Teams, projects, or work item types contributing most to remaining work
- Areas where scope accumulates faster than it is completed