Commit Velocity Calculator
Track commit velocity trends across a team or repository over multiple sprints.
About Commit Velocity Calculator
Commit velocity tracks throughput over time. Formula: velocity = commits / weeks, benchmarked against a team or organization average to see whether a repository or contributor is pacing above, at, or below the norm. As with commit frequency, this is a volume metric, not a value or quality metric — use it alongside review and defect data.
Formula
velocity = commits / weeks
- commits
- Total commits in the period
- weeks
- Length of the period in weeks
Worked example
With the default values below, Commit Velocity Calculator returns Commit Velocity of 40.00. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Total Commitsaccepts 0–10,000,000 commits
- 320 commits
- Period Lengthaccepts 0.1–5,200 weeks
- 8 weeks
- Team/Org Average Velocityaccepts 0–1,000,000 commits/week
- 35 commits/week
Results
- Commit Velocity
- 40.00 /week
- vs. Team Average
- Above average
- Difference from Average
- 14.3%
Step by step
- 1Velocity: commits / weeks= 40.00/week
- 2Difference from team average= 5.00/week (14.3%)
Assumptions and limits
- The result is derived only from the 3 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or fees or charges into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is this different from commit frequency (per day)?
It's the same underlying idea at a different granularity — velocity uses weekly buckets, which smooths out day-to-day noise like weekends and is more common for sprint-based team comparisons.
Should I use commit velocity to evaluate individuals?
Be cautious — commit count varies hugely with style (squash vs. incremental commits), task type (a one-line config fix vs. a complex feature), and can be gamed if used punitively. It's better suited to repository/team trend analysis.
What causes velocity to differ across teams fairly?
Team size, codebase maturity (greenfield vs. legacy), and task complexity all legitimately shift velocity — always contextualize a comparison against team average with these factors.
How do I compute a team average baseline?
Aggregate commits per week across all repositories/teams in your org over a representative period (e.g. a quarter) and divide by team-weeks to get a fair per-team average.