Agile velocity chart gadget: 10 sprint metrics, KPI reports

Capacity-adjusted views help us interpret velocity during holidays and reduced staffing. The chart has made forward planning more realistic than simply averaging the last three sprints.

Benchmarks based on averages, medians, and percentiles give useful context across our Scrum teams without setting one universal target. We use them as coaching signals, not as a league table.

The issue breakdown explains why a sprint number changed. We can see what was added, removed, re-estimated, or rolled over and open the corresponding Jira items directly

Say-do ratio and scope-change metrics give us a clearer picture of predictability. A stable completed total can hide constant replanning, and this chart makes that visible.

The cross-team chart lets us compare eleven teams without maintaining eleven spreadsheets. We use it to identify unusual trends, then talk to teams about context rather than ranking them blindly.