GitHub Metric
Engineering
Sprint Velocity = Sum of Story Points (or Issue Count) Completed in Sprint
Sprint Velocity Tracking measures the amount of work - typically in story points or issue count - completed during each sprint or iteration, as tracked through GitHub Projects. It provides a baseline for capacity planning and helps teams set realistic commitments for upcoming sprints.
GitHubEngineeringSprint Velocity Tracking
Sprint Velocity Tracking measures the amount of work - typically in story points or issue count - completed during each sprint or iteration, as tracked through GitHub Projects. It provides a baseline for capacity planning and helps teams set realistic commitments for upcoming sprints.
How to calculate sprint velocity tracking
Why sprint velocity tracking matters for GitHub users
Without a reliable velocity baseline, sprint commitments are guesswork. Teams either over-commit and burn out or under-commit and waste capacity. Consistent velocity tracking builds the data foundation for predictable delivery.
For GitHub teams using Projects, velocity tracking closes the loop between planning and execution. It highlights sprints disrupted by unplanned work, helping teams protect capacity for planned commitments and negotiate scope more effectively with stakeholders.
Understand and act on sprint velocity tracking with KPI Tree
Extract sprint completion data from GitHub Projects into your warehouse and track velocity in KPI Tree. Place it alongside feature cycle time and bug fix rate to understand how velocity relates to quality and delivery speed.
Assign RACI ownership to scrum masters or delivery leads and use rolling averages rather than single-sprint figures for more stable capacity planning.
Get started with your GitHub data
MCPPull metrics from GitHub directly through the Model Context Protocol.
Connect your existing warehouse where GitHub 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 GitHub metrics
Feature Development Cycle Time
EngineeringMetric Definition
Cycle Time = Deployment Timestamp − First Feature Commit Timestamp
Feature Development Cycle Time measures the elapsed time from the first commit on a feature branch to successful deployment to production. It encompasses coding, review, testing, and release phases. Shorter cycle times enable faster user feedback and more responsive product development.
Issue Resolution Time
EngineeringMetric Definition
Issue Resolution Time = Issue Closed Timestamp − Issue Created Timestamp
Issue Resolution Time measures the elapsed time from when a GitHub issue is opened to when it is closed. It reflects team responsiveness, prioritisation effectiveness, and overall execution speed. Segmenting by label (bug, feature, chore) provides more actionable insights.
Release Velocity
EngineeringMetric Definition
Release Velocity = Number of Releases / Time Period
Release Velocity measures the frequency and speed at which new versions are tagged and published via GitHub Releases or deployment workflows. It encompasses the cadence of releases, the volume of changes per release, and the time between successive releases. Healthy velocity balances speed with stability.
Developer Productivity Score
EngineeringMetric Definition
Developer Productivity Score is a composite metric that blends output indicators (commits, PRs merged), quality signals (review depth, test coverage), and collaboration measures (reviews given, discussions participated in). It provides a balanced view of developer effectiveness that avoids over-indexing on raw output.
All GitHub metrics
Branch Lifecycle AnalysisBug Fix RateCode Churn RateCode Coverage TrendCode Quality Trend AnalysisCode Review Quality ScoreCode Review VelocityCommit FrequencyDeployment FrequencyDeveloper Contribution PatternsDeveloper Productivity ScoreDevOps Pipeline EfficiencyDiscussion Engagement RateFeature Development Cycle TimeIssue Resolution TimeLead Time for ChangesOpen Source Contribution AnalysisPull Request Approval RatePull Request Bottleneck AnalysisRelease VelocityRepository Health ScoreSecurity Alert Resolution TimeSecurity Vulnerability TrendsTeam Collaboration IndexTechnical Debt AccumulationEmpower your team to understand and act on GitHub data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
