Added Work Items Not Completed
Added Work Items Not Completed measures the number of distinct Jira work items that were added to a sprint after it started and were not completed by the time the sprint is completed.
It represents unplanned work that was introduced during the sprint but not delivered within the sprint.
This Metric does not measure total delivery volume, effort, or planning quality. It focuses only on the outcome of work introduced after sprint commitment.

What Question Does Added Work Items Not Completed Answer?
Added Work Items Not Completed is designed to answer:
What work added mid-sprint was not completed by sprint completion?
How Work Items Are Counted
Added Work Items Not Completed is calculated using sprint boundary snapshots.
A work item is included if:
- It was not part of the sprint at sprint start
- It was assigned to the sprint after sprint start
- It is not in a status mapped to the Completed lifecycle state at sprint completion
Each work item is counted once per sprint.
When a Time dimension is applied, sprints are grouped based on their completion time. Only sprints whose completion time falls within the selected time period are included. The Metric is calculated once per sprint and then aggregated across sprints. Work items are not deduplicated across sprints, as each sprint represents a separate execution context.
Configuration
Added Work Items Not Completed 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 Added Work Items Not Completed
Added Work Items Not Completed is commonly used to analyse:
Delivery Spillover
- Amount of added work pushed beyond the sprint
- Frequency of incomplete unplanned work
Interruption Cost
- Impact of mid-sprint additions on delivery focus
- Trade-offs between reactive work and planned commitments
Execution Limits
- Capacity constraints when absorbing new work
- Patterns where added work consistently fails to complete