📈 Agile Metrics: Velocity, Burndown & Burnup Explained

Sprint Health Analyzer provides three core Agile metrics to help teams evaluate sprint progress and delivery trends over time:

• Velocity – how much work the team completed

• Burndown – how work was reduced each day

• Burnup – how scope and progress evolved together

These charts appear in the Agile Metrics mode of the app. You can switch to this view by clicking the "Agile Metrics" button and optionally adjust the sprint dates using the built-in date pickers.

To ensure metrics are accurate:

A snapshot of how many story points were completed during the selected sprint.

• Completed story points (from issues marked Done before sprint end)

• Total sprint scope (sum of all story points in scope)

velocity = SUM(storyPoints WHERE doneAt <= sprintEnd) totalScope = SUM(storyPoints of all sprint issues)

• The bar represents completed work

• The subtitle shows velocity vs total scope (e.g. Velocity: 21 / 34)

• The percentage helps teams assess sprint delivery capacity

Tracks how many story points remain each day vs. ideal progress.

• Actual remaining story points per day

• Ideal linear trend from total scope → 0

remaining[day] = SUM(storyPoints of issues NOT done on or before day) ideal[day] = totalScope - (totalScope / (days - 1)) * dayIndex

• Ideal burndown assumes uniform progress across all sprint days.

• Completed issues reduce the "remaining" value each day.

• If the actual line stays above the ideal → progress is behind

• If the actual line drops faster → you're ahead of schedule

• Flat spots = no completion; upward spikes = scope increased mid-sprint

Visualizes cumulative work completed alongside evolving scope.

• Completed work (cumulative story points Done by day)

• Total scope (including issues added mid-sprint)

completed[day] = SUM(storyPoints WHERE doneAt <= day) totalScope[day] = SUM(storyPoints WHERE addedAt <= day)

• This chart accounts for scope creep: issues added after sprint start still contribute to scope line.

• The gap between completed and total scope = remaining work

• If scope line goes up mid-sprint → new work was added

• If lines are close together → good alignment between commitment and delivery

• Velocity is not a productivity metric — it only reflects completion rate

• Burndown assumes linear ideal progress — it’s a guide, not a rule

• Burnup requires that storyPoints and addedAt (or created date) are populated