Sprint Work Items Added
Sprint Work Items Added measures the number of distinct Jira work items that are introduced into a sprint after it has started.
It represents changes to 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 Added Answer?
Sprint Work Items Added is designed to answer:
How much work was introduced into the sprint after the team had already committed?
How Work Items Are Counted
Sprint Work Items Added is calculated using sprint boundary snapshots.
A work item is included if:
- It was not part of the sprint at sprint start
- It is assigned to the sprint at any point after the sprint begins
Each work item is counted once per sprint. Work items added and later removed are still included, as they represent scope change after commitment. This Metric tracks sprint membership changes, not work item creation.
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 Added 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 Added
Sprint Work Items Added is commonly used to analyse:
Scope Volatility
- How frequently work is introduced mid-sprint
- Sprints with high levels of unplanned or interrupt-driven work
Planning Disruption
- Impact of incidents, escalations, or urgent requests
- Degree to which sprint commitment is being altered
Predictability Risk
- Relationship between mid-sprint additions and delivery shortfalls
- Early warning signals of unstable sprint execution