Sprint Story Points Metrics

Sprint Story Points Metrics measure how much effort a team plans, delivers, and changes during a sprint using story points.

They provide an effort-based view of sprint execution, focusing on planned vs delivered work and changes in scope.

Unlike work item-based Sprint Metrics, these Metrics measure effort, not the number of work items or flow.

What These Metrics Help You Understand

Sprint Story Points Metrics are designed to help answer:

  • How much effort was committed at sprint start?
  • How much effort was delivered by sprint completion?
  • How much scope changed during the sprint?
  • How predictable is sprint delivery in terms of effort?

How Sprint Story Points Metrics Work

Sprint Story Points Metrics are based on two sprint reference points:

  • Sprint start snapshot — defines the committed and added scope baseline in story points
  • Sprint completion snapshot — determines what effort was delivered by sprint completion

Story points are aggregated from work items, but the Metrics represent total effort, not work item count.

Core Principles

Sprint Story Points Metrics follow these principles:

  • Commitment is fixed at sprint start — work items are classified as Committed or Added at sprint start, and this classification does not change
  • Effort-based measurement — story points are summed to represent effort, regardless of how many work items are involved
  • Scope changes are tracked explicitly — removed includes any work item whose story points leave the sprint after sprint start
  • Completion is evaluated at sprint completion — story points are considered completed if the work item is in the Completed lifecycle state at sprint completion

Choosing the Right Sprint Story Points Metric

  • Sprint Story Points Committed — use this to understand the planned effort the team took on at sprint start
  • Sprint Story Points Completed — use this to measure total delivered effort by sprint completion, including added scope
  • Sprint Story Points Added — use this to track unplanned effort introduced after sprint start
  • Sprint Story Points Removed — use this to track effort de-committed after sprint start
  • Sprint Story Points Completed from Commitment — use this to measure delivery against the original committed effort
  • Sprint Story Points Not Completed from Commitment — use this to identify committed effort that was not finished by sprint end
  • Sprint Story Points Completed from Added Scope — use this to see how much added effort was still delivered within the sprint
  • Sprint Added Story Points Not Completed — use this to track added effort that was not completed by sprint end

When to Use These Metrics

Sprint Story Points Metrics are best used to analyse:

  • Effort commitment and delivery
  • Sprint predictability and reliability
  • Changes in scope during execution
  • Team capacity trends over time

They are most effective when used alongside work item-based Metrics to provide a complete view of sprint performance.

Metrics in this category

For AI agents: the complete documentation index is available at https://dashlytics-docs.vivek-fitkariwala.workers.dev/llms.txt, the full documentation bundle is available at https://dashlytics-docs.vivek-fitkariwala.workers.dev/llms-full.txt, and this page is available as Markdown at https://dashlytics-docs.vivek-fitkariwala.workers.dev/reference/metrics/sprint-story-points-metrics/index.md.