---
updatedAt: 2026-11-05T00:13:15.000Z
agentTools:
  projectIndex: https://docs.atono.io/llms.txt
---

# Story throughput

Understand how much work your team completes over time and how its delivery rate is changing.

Story throughput is a report that shows how many stories a team completed in each week, month, or sprint, as a count of stories or as story points. It counts stories only, not bugs.

To see how long stories and bugs take to complete, use [Cycle time over time](https://docs.atono.io/docs/cycle-time#cycle-time-over-time) instead. To follow the story points left in a single sprint day by day, use a [burndown chart](https://docs.atono.io/docs/burndown-charts).

To open the report, select **Story throughput** from the report selector on a team's [Analytics](https://docs.atono.io/docs/analytics) tab. Anyone in the workspace can view it for any team, including private teams.

<br />

***

# View stories or story points

Select **Story** to see how many stories were completed in each period, or **Story points** to see their total story points. Each story's points come from its size, using Atono's [standard point values](https://docs.atono.io/docs/total-story-points#how-total-story-points-are-calculated). For example, an L story adds 8 points and an XS story adds 2. The summary cards, chart, trend, and projection all use the measure you select.

<br />

***

# Change the timeframe

1. Next to 'Show last', enter a number and select **weeks** or **months**.
2. From 'View', select:
   * **weekly** to make each bar a week.
   * **monthly** to make each bar a month.
   * **sprints** to make each bar a sprint. This option is only available for Scrum teams.

In sprints view, the chart shows only the sprints that started within the timeframe, including the active sprint. A sprint that started before the timeframe isn't shown, even if it ended within it, so choose a timeframe that reaches back to the start of the earliest sprint you want to see.

<br />

***

# Understand the report

<br />

## Summary

The cards above the chart each show their date range:

* 'Total stories' or 'Total story points' covers the whole timeframe up to now, including what's been completed so far in the current period.
* 'Weekly average', 'Monthly average', or 'Sprint average' covers full periods only. It leaves out the current period, and also the first period when the timeframe starts partway through a week or month.

<br />

## Chart

Each bar shows the stories or story points completed in one period. If nothing was completed in a period, its label still appears along the bottom of the chart, with no bar above it.

Two kinds of bar look different from the rest:

* **Current period**: The solid part of the bar shows what's been completed so far, and a dashed outline shows the [projected total](#projections) for the full period.
* **Orange corner**: An orange triangle in a bar's top-right corner marks a partial first period, when the timeframe starts partway through a week or month. In 'Story points' view, it also marks bars whose totals include approximated story points.

The current period and a partial first period count toward the total, but not toward the average or the trend.

When some completed stories are unsized, 'Story points' view approximates their points. Besides the orange triangles, a warning icon appears on each summary card, and a 'Missing story points' note appears below the chart. Hover over a card's warning icon to see how many stories were approximated. For how the approximation works, see [Missing story point estimates](#missing-story-point-estimates).

If no stories were completed in the timeframe, the cards show '--' and the chart shows 'No stories to display'. In 'Story points' view, they're also empty when none of the completed stories have a size. The chart then shows 'No story points to display', and the note below it offers a link to switch to story view.

<br />

## Hover details

Hover over a bar to see a pop-up with:

* The period's dates, or the sprint's name and dates.
* The number of stories and their story points, with the measure you selected shown first.
* A breakdown by story size, from XXS to XXL, with the number of stories and story points for each size that has at least one story. In 'Story points' view, approximated stories are listed last as 'Unsized', with a tilde (\~) before their points.

Since an orange triangle can mark either a partial first period or approximated story points, check the pop-up to see which: it says 'Partial week' or 'Partial month' for a partial period, and lists an 'Unsized' row for approximated points.

<br />

## Trend

The dashed 'Trend' line shows whether throughput is generally rising, falling, or holding steady across the timeframe. Individual periods vary above and below it, so read it as the overall direction rather than as a target for any one period.

<br />

## Projections

The projection estimates how many stories or story points the team will complete by the end of the current period, based on the team's average in earlier periods. It isn't a forecast for specific stories.

Hover over the current period to see the projected total in the pop-up's 'Projected' section, along with the full period's dates in weekly and monthly views. The section only appears while the projection is higher than what's already been completed.

<br />

***

# View completed stories

If you're not a member of a private team, you can't open its stories. Instead, the bar's pop-up says 'You don't have permission to view items on this team's backlog.'

Click a bar in the chart. The Everything page opens with only stories shown, filtered by:

* The team.
* 'Workflow step: Any step in 'Done' category'.
* 'Completed', set to the period's dates.

<br />

***

# How Story throughput is calculated

<br />

## What counts as completed

The report counts the team's stories that are in a step in the 'Done' category, in the period when each one was completed. Sample data isn't counted, but stories marked as [outliers](https://docs.atono.io/docs/cycle-time#outliers) are.

The report always reflects each story's current state, so earlier periods can change:

* A story that's reopened drops out of the report. If it's completed again later, it counts in the period when it was completed again.
* A story moved to 'Won't do' after being completed no longer counts.
* A story moved to another team no longer counts for this team. If it's still completed on its new team, it counts for that team instead.
* Changing a completed story's size changes the story points it adds to its period.

<br />

## Periods and time zone

Periods are based on the [team's time zone](https://docs.atono.io/docs/teams#set-team-time-zone), which the report names below its controls. Weeks run from Monday to Sunday, and months are calendar months. The timeframe starts the chosen number of weeks or months before today, so when that date isn't a Monday or the first of a month, the first period is partial.

In sprints view, each bar uses its sprint's start and end dates. Stories completed outside the sprints shown, such as between two sprints or before the first one, aren't counted.

<br />

## Averages, trends, and projections

The average on the summary card is the total for all full periods divided by the number of full periods, including periods when nothing was completed. The trend line is a straight line fitted to the same full periods, and it appears once there are at least two of them.

The projection averages earlier full periods in the same way, but it can be limited by the team's [cycle time window](https://docs.atono.io/docs/cycle-time#configure-the-cycle-time-averaging-window), so it can differ from the average on the summary card. Stories and story points are projected separately, each from the team's average for that measure. In sprints view, the active sprint's projection can also differ from the projections on its [burndown chart](https://docs.atono.io/docs/burndown-charts#projection-active-sprints-only) and the [Sprint calendar](https://docs.atono.io/docs/sprint-calendar#understanding-sprint-capacity-and-projection), since each is calculated differently.

<br />

## Missing story point estimates

When some of the stories completed in the timeframe are unsized, 'Story points' view counts each unsized story as the median size of the sized stories completed in the same timeframe. For example, if the median sized story is M, each unsized story counts as 5 points.

Total story points and burndown charts estimate unsized stories differently, so the same unsized story can count for a different number of points there.

<br />

## Limits and saved settings

'Show last' accepts 1 to 260 weeks or 1 to 60 months, and it's set to 3 months until you change it.

Your view and timeframe selections are saved for you and apply to every team's report you open, but they aren't shared with the cycle time reports. If you've selected 'sprints' and then open a Kanban team's report, the view changes to 'weekly'.

<br />