Sprint Story Points Completed from Added Scope

Sprint Story Points Completed from Added Scope measures the total number of story points that were added to a sprint after it started and were completed by the time the sprint is completed.

It represents the delivery outcome of unplanned or newly introduced effort, expressed in story points.

This Metric does not measure total delivery, planning accuracy, or commitment reliability. It focuses only on how much added scope was completed within the sprint.

Report table showing the Sprint Story Points Completed from Added Scope Metric

What Question Does Sprint Story Points Completed from Added Scope Answer?

Sprint Story Points Completed from Added Scope is designed to answer:

How many of the story points added after sprint start were completed by sprint completion?

How Story Points Are Counted

Sprint Story Points Completed from Added Scope is calculated using sprint boundary snapshots.

Story points are included if the work item was not part of the sprint at sprint start and is in a status mapped to the Completed lifecycle state at sprint completion. Story points are summed from all completed added work items. Story points from originally committed work items are excluded, even if they are completed.

When a Time dimension is applied, sprints are grouped based on their completion time. Each sprint contributes one value representing completed added story points. 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 execution context.

Configuration

Sprint Story Points Completed from Added Scope 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 Completed from Added Scope

Sprint Story Points Completed from Added Scope is commonly used to analyse:

Responsiveness

  • How much unplanned effort the team can absorb and still deliver
  • Handling of urgent requests, incidents, or escalations within the sprint

Impact of Interruptions

  • How much mid-sprint added scope was successfully completed
  • Trade-offs between reactive and planned delivery

Execution Trade-offs

  • Relationship between completed added scope and unfinished committed scope
  • Cost of scope volatility on original sprint commitments
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/sprint-story-points-completed-from-added-scope/index.md.