Sprint Story Points Committed
Sprint Story Points Committed measures the total number of story points that were part of the sprint commitment at the moment the sprint started.
It represents the planned effort the team committed to deliver at sprint start, expressed in story points.
This Metric does not measure delivery, progress, or completion. It focuses only on the planned workload size at the beginning of the sprint.

What Question Does Sprint Story Points Committed Answer?
Sprint Story Points Committed is designed to answer:
How much effort (in story points) did the team commit to at the start of the sprint?
How Story Points Are Counted
Sprint Story Points Committed is calculated using a snapshot taken at sprint start.
Story points are included if the work item is part of the sprint at sprint start. Story points are summed from all committed work items. Work items added or removed after sprint start are excluded. Changes to story point values after sprint start do not affect the result.
When a Time dimension is applied, sprints are grouped based on their committed time. Each sprint contributes one committed story point value. The Metric is calculated once per sprint and then aggregated across sprints. Story points are not deduplicated across sprints, as each sprint represents a separate commitment context.
Configuration
Sprint Story Points Committed 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 Sprint Story Points Committed
Sprint Story Points Committed is commonly used to analyse:
Sprint Planning Behaviour
- Typical commitment size per sprint
- Variability in planned workload across sprints
- Differences in commitment between teams or projects
Capacity Expectations
- Expected delivery capacity expressed in effort
- Comparison of planned effort vs delivered effort
Predictability Foundations
- Baseline for velocity and predictability metrics
- Analysis of over-commitment or under-commitment trends
- Long-term stability of sprint planning practices