---
title: "Iteration completion"
canonical_url: "https://docs.getdx.com/reports/iteration-completion/"
md_url: "https://docs.getdx.com/reports/iteration-completion.md"
last_updated: "2026-06-08"
---

# Iteration completion
The **Iteration completion** report measures the percentage of total iteration work that was finished, including both planned and unplanned work items. Use this metric to evaluate overall throughput and closure rate across your iterations.

> Note: Iteration completion is only available when Azure DevOps is connected to DX.

![Iteration completion report in DX](https://docs.getdx.com/assets/images/reports/iteration-completion.png)

## When to use iteration completion

Iteration completion answers the question: _How much of everything in the iteration did we finish?_

This report helps teams:

- **Measure overall throughput** — Understand how much total work the team closed out during the iteration, regardless of when it was added.
- **Track closure rate** — Identify whether work is accumulating or being consistently completed.
- **Account for scope changes** — Get a realistic view of iteration execution that reflects mid-iteration adjustments.

## How completion percentage is calculated

The completion percentage is calculated as:

**Completed work ÷ Total work**

Where:

- **Completed work** is the story point/work item count for all work items marked complete during the iteration
- **Total work** is the story point/work item count for all work items in the iteration, whether planned or unplanned

This metric captures the full picture of iteration execution, including any work added after the iteration started. Iteration completion can be calculated based on either story points or work item counts.

In ADO, iterations can be nested, with work items spanning multiple levels of a tree. DX only reports on “leaf node” iterations—iterations that do not have any children or sub-iterations.

## Understanding planned vs. unplanned work

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

## How iteration completion differs from iteration predictability

Unlike [iteration predictability](https://docs.getdx.com/reports/iteration-predictability/), iteration completion measures against the final scope, including work added mid-iteration.

For example, if you add 10 points mid-iteration but do not finish them:

- Your **Completion** score drops (because the total scope increased).
- Your **Predictability** score stays the same (because it ignores items added after the iteration started).

Use iteration completion to see if scope creep is preventing you from closing out iterations, and iteration predictability to see if you are delivering the volume you originally promised.
---

## Sitemap

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