AGILE

Mobile Team Velocity Trend

This chart shows completed story points for a mobile team across six sprints and marks a 25-point planning average. The bars reveal normal variation without pretending that capacity is fixed. A team can use the recent pattern to choose a conservative planning range, then inspect any large change for causes such as production support, holidays, or changes in the definition of done. The planning average is a guide, not a quota. It should be updated when the team changes materially, for example after adding people or altering sprint length. Keep velocity conversations focused on the team's own forecast and improvement work rather than comparisons with other teams.

UPDATED 2026-09-25

TYPEBar

EXAMPLEMobile Team Velocity Trend

Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Setting a mobile sprint forecast

Key decisions

Baseline: Use a recent average rather than the best sprint.
Outliers: Discuss causes of unusually low or high results.
Scope: Keep the measurement to completed work.

When to reuse this

Use this view when a team needs a simple capacity baseline for its next sprint.

FAQ

Frequently asked questions

What is a planning average?01

It is a recent completed-velocity baseline used to help a team select a realistic amount of work.

Should velocity always increase?02

No. Stable, sustainable delivery is often more useful than pushing a metric upward.

What can lower a sprint's velocity?03

Interruptions, leave, unplanned support, changed scope, or work that was not finished can all affect it.

Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.