Sprint Work Items Removed
Sprint Work Items Removed measures the number of distinct Jira work items that are removed from a sprint after it has started.
It represents reduction in sprint scope after the team has already committed.
This Metric does not measure delivery, effort, or completion. It focuses only on scope change during the sprint.

What Question Does Sprint Work Items Removed Answer?
Sprint Work Items Removed is designed to answer:
What work was taken out of the sprint after it had already started?
How Work Items Are Counted
Sprint Work Items Removed is calculated using sprint boundary snapshots.
A work item is included if:
- It is assigned to the sprint at any point after sprint start
- It is removed from the sprint before sprint completion
Each work item is counted once per sprint, even if it is removed multiple times. Work items that are added and then removed within the same sprint are still included, as they represent scope churn during execution. This Metric tracks sprint membership changes, not work item resolution or deletion.
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 commitment context.
Configuration
Sprint Work Items Removed 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 Work Items Removed
Sprint Work Items Removed is commonly used to analyse:
Scope Reduction
- Frequency of work being taken out mid-sprint
- Sprints with significant de-commitment
Planning Accuracy
- Over-commitment patterns
- Late realisation that work cannot be completed
Execution Instability
- Priority churn during the sprint
- Relationship between removals and missed sprint goals