---
title: "Sprint volatility"
canonical_url: "https://docs.getdx.com/reports/sprint-volatility/"
md_url: "https://docs.getdx.com/reports/sprint-volatility.md"
last_updated: "2026-06-08"
---

# Sprint volatility
The **Sprint volatility** report measures how much the sprint scope changed after the sprint started. Use this metric to identify scope creep, unplanned interruptions, or issues with sprint locking practices.

![Sprint volatility report in DX](https://docs.getdx.com/assets/images/reports/sprint-volatility.png)

## When to use sprint volatility

Sprint volatility answers the question: _How much did the scope change mid-sprint?_

This report helps teams:

- **Identify scope creep** — Understand how often new work is being added after sprint planning.
- **Spot process issues** — High volatility may indicate poor sprint locking discipline or frequent interruptions.
- **Explain low predictability** — When [sprint predictability](https://docs.getdx.com/reports/sprint-predictability/) is low, high volatility is often the cause.

## How volatility percentage is calculated

The volatility percentage is calculated as:

**Unplanned work ÷ Total work**

Where:

- **Unplanned work** is the story point/issue count for issues added after the sprint started
- **Total work** is the story point/issue count for all issues in the sprint, whether planned or unplanned

This metric specifically tracks items where `planned = false`—issues that were added after the sprint start date. Sprint volatility can be calculated based on either story points or issue counts.

## Understanding planned vs. unplanned work

| Term                 | Definition                                                                                        |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| **Planned points**   | Story points for issues that existed in the sprint at the sprint start time                       |
| **Unplanned points** | Story points for issues added after the sprint started                                            |
| **Completed points** | Story points for all issues marked complete during the sprint, regardless of when they were added |

## How sprint volatility relates to other sprint metrics

Sprint volatility provides context for interpreting [sprint completion](https://docs.getdx.com/reports/sprint-completion/) and [sprint predictability](https://docs.getdx.com/reports/sprint-predictability/):

- **High volatility + low predictability** — Suggests that scope creep is disrupting the team's ability to deliver on commitments.
- **High volatility + high completion** — Indicates the team is absorbing additional work and still closing it out, but may be at risk of burnout or unsustainable pace.
- **Low volatility** — Suggests strong sprint discipline, making predictability a more reliable measure of planning accuracy.
---

## Sitemap

[Overview of all docs pages](/llms.txt)