Mobile Team Velocity Trend Chart

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.

Typ BalkendiagrammEngine echarts-barAktualisiert 24.9.2026

Die Anfrage

“Create a velocity chart for the Mobile Team showing completed story points for Sprints 14 to 19 of 22, 25, 24, 27, 23, and 26, with a 25-point planning average line.”

Dann probieren SieChange the planning average to 24 points.Add Sprint 20 with 28 completed points.

Was diese Zeichnung zeigt

Die dahinterstehenden Entscheidungen verstehen.

01Baseline

Use a recent average rather than the best sprint.

02Outliers

Discuss causes of unusually low or high results.

03Scope

Keep the measurement to completed work.

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

Alle Balkendiagramm-Vorlagen durchsuchen →

FAQ

Häufige Fragen

What is a planning average?

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

Should velocity always increase?

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

What can lower a sprint's velocity?

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