Velocity & Throughput Metrics

Understand your team's delivery capacity with real-time velocity tracking, throughput analysis, and sprint performance insights that help you plan better and deliver more consistently.

Velocity Dashboard
Benchmarks

Key Velocity Indicators

Track these metrics to understand your team's delivery rhythm and forecast capacity accurately.

Planned

32

Story Points

Completed

28

Story Points

Average

26

Last 5 Sprints

Spillover

12%

Rate

Throughput

18

Items/Sprint

Velocity

What is Velocity?

Velocity represents the amount of work a team completes during a sprint or iteration. It is calculated using completed work items that meet the team's Definition of Done.

Example: Stories completed → 5 + 3 + 8 story points = Velocity 16

Use velocity for sprint planning and capacity forecasting — but remember, it's most meaningful when tracked consistently over time within a single team.

📊
+23% vs Last Sprint
Velocity Metrics
MetricDescription
Planned VelocityTotal story points committed at sprint planning
Actual VelocityTotal story points completed in the sprint
Average VelocityAverage velocity from last 3–5 sprints
Committed vs CompletedMeasures delivery against commitment
Spillover RateWork moved to the next sprint
Throughput

Throughput Metrics

Throughput measures work items completed during a time period — focusing on item count rather than effort estimation. It provides a more objective view of delivery capacity.

Unlike velocity, throughput is easier to compare across teams since it doesn't rely on subjective story point estimates.

18 Items This Sprint
94% Completion
Throughput Flow
MetricDescription
Total Items CompletedTotal number of completed tasks, bugs or stories
Weekly / Daily ThroughputItems completed per day or week
Throughput by TypeBreakdown by feature, bug, or technical task
WIP CountItems currently being worked on
Comparison

Velocity vs Throughput

Understanding when to use each metric for planning and delivery tracking.

AspectVelocityThroughput
UnitStory Points / EffortNumber of Work Items
FocusTeam CapacityWork Flow Efficiency
UsagePlanning & ForecastingDelivery Speed Tracking
ComparisonNot recommended across teamsMore comparable
Engineering Activity

Engineering Activity Metrics

Granular signals of development health and CI/CD pipeline effectiveness.

Commits per Developer

Shows development contribution activity in a sprint.

Pull Requests Merged

Measures completed code integrations.

Code Churn Rate

Identifies rewritten code and instability.

Builds Triggered

CI/CD pipeline activity and build frequency.

Test Coverage Change

Improvement in automated testing coverage.

Lead Time for Changes

Time from code commit to production deployment.

Code velocity
Commits per developer per sprint
LoC added / changed per sprint
PRs merged per sprint
Merged Closed
Code churn rate
14%
Builds triggered per sprint
Lead time for changes
4.2days
Effort distribution
Features45%
Bug fixes25%
Refactor20%
Docs10%
Features
45%
Bug fixes
25%
Refactor
20%
Docs
10%
Developer active days per sprint
Overall repo health
CommitsImproving
PR mergesDeclining
LoCWatch
ChurnStable

Track What Your Teams Actually Deliver

Get accurate velocity and throughput metrics that help your teams plan better and deliver more consistently.

Request a Demo