Jira Metric
Issue Tracking
Sprint Velocity = Total Story Points Completed per Sprint
Sprint Velocity measures the total story points or issue count completed by a team in each Jira sprint. It provides a rolling baseline of team capacity that is used for forecasting future delivery and calibrating sprint commitments.
Full guide: definition, formula, and benchmarksSprint Velocity
Sprint Velocity measures the total story points or issue count completed by a team in each Jira sprint. It provides a rolling baseline of team capacity that is used for forecasting future delivery and calibrating sprint commitments.
How to calculate sprint velocity
Why sprint velocity matters for Jira users
Velocity is the foundation of agile forecasting. A stable velocity enables teams to predict with confidence how much work they can deliver in upcoming sprints and when larger initiatives like epics will be completed.
For Jira teams, velocity trends reveal the impact of team changes, process improvements, and external factors on delivery capacity. It helps product managers set realistic expectations and provides teams with an objective basis for sprint planning commitments.
Understand and act on sprint velocity with KPI Tree
KPI Tree calculates sprint velocity from your Jira data warehouse, displaying trends and rolling averages. Place this at the core of your capacity planning tree, feeding into epic progress and release burnup metrics.
Assign RACI ownership to scrum masters for velocity tracking and team leads for capacity decisions. Set alerts for significant velocity deviations from the rolling average.
Get started with your Jira data
Pull metrics from Jira directly through the Model Context Protocol.
Connect your existing warehouse where Jira data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related Jira metrics
Sprint Commitment Accuracy
Issue TrackingMetric Definition
Commitment Accuracy = (Completed Committed Points / Total Committed Points) × 100
Sprint Commitment Accuracy measures the percentage of committed sprint scope that a team actually delivers by the end of the sprint in Jira. It compares what was planned at sprint start against what was completed at sprint end, excluding work added mid-sprint.
Sprint Burndown Analysis
Issue TrackingMetric Definition
Sprint Burndown Analysis tracks the remaining work in a Jira sprint over time, comparing actual progress against the ideal burndown trajectory. It reveals whether the team is on track to complete their sprint commitment and surfaces mid-sprint risks.
Epic Progress Tracking
Issue TrackingMetric Definition
Epic Progress = (Completed Story Points / Total Epic Story Points) × 100
Epic Progress Tracking monitors the advancement of Jira epics by measuring the proportion of child issues completed, story points delivered, and time elapsed against planned timelines. It provides feature-level visibility into delivery progress.
Cycle Time
Issue TrackingMetric Definition
Cycle Time = Done Date − In Progress Date
Cycle Time measures the elapsed time from when work actively begins on a Jira issue (typically moving to "In Progress") to when it is marked done. It captures the actual working duration, excluding backlog waiting time, and is a key indicator of process efficiency.
Explore sprint velocity across integrations
All Jira metrics
Empower your team to understand and act on Jira data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.