Track commit velocity trends across a team or repository over multiple sprints.
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.
velocity = commits / weeks
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.
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.
Team size, codebase maturity (greenfield vs. legacy), and task complexity all legitimately shift velocity — always contextualize a comparison against team average with these factors.
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.