Sprint Metrics

Sprint Metrics provide visibility into commitment, delivery, and scope change for Scrum teams working in time-boxed sprints.

Unlike flow or backlog Metrics, Sprint Metrics evaluate work within sprint boundaries, using snapshots at sprint start and sprint completion to assess execution quality and predictability.

Sprint Metrics are designed to answer short-cycle execution questions, not long-term system health or continuous flow behaviour.

How Sprint Metrics Work

Sprint Metrics are based on two fixed sprint reference points:

  • Sprint Start — represents the team's commitment at the beginning of the sprint
  • Sprint Completion — represents the team's delivery outcome at the moment the sprint is actually completed, not the planned end date

Dashlytics evaluates sprint completion using the actual sprint completion event in Jira.
This ensures sprint metrics reflect when the sprint truly ended, even if it was completed earlier or later than planned.

What Sprint Metrics Are Designed to Answer

Sprint Metrics help teams understand:

  • How much work was committed at sprint start
  • How much work was completed by sprint completion
  • How predictable sprint delivery is
  • How much scope changed during the sprint
  • Whether unplanned work disrupted execution

These Metrics focus on execution quality and predictability, not effort, duration, or flow efficiency.

Choosing the Right Sprint Metric

Each Sprint Metric is designed to answer a specific question. Choose the Metric that best matches the insight you are looking for:

  • Sprint Work Items Committed — use this to understand how much work the team took on at sprint start
  • Sprint Work Items Completed — use this to measure how much work was finished by the end of the sprint
  • Sprint Work Items Added — use this to track unplanned scope introduced after sprint start
  • Sprint Work Items Removed — use this to track work removed from the sprint after it started
  • Committed Work Items Completed — use this to measure delivery against the original commitment
  • Committed Issues Not Completed — use this to identify committed work that was not finished by sprint end
  • Added Issues Completed — use this to see how much added scope was still delivered within the sprint
  • Added Issues Not Completed — use this to track added scope that was not completed by sprint end

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-metrics/index.md.