Skip to content
ENExplore Calculators

Release Velocity Calculator

Calculate release velocity trends across sprints to track delivery acceleration.

About Release Velocity Calculator

Release velocity normalizes release counts from two consecutive periods to a common releases-per-week rate and compares them to detect a trend: change% = (current_velocity − previous_velocity) ÷ previous_velocity × 100. A change beyond ±5% is classified as accelerating or decelerating; smaller fluctuations are treated as stable, since release counts over short periods naturally have some noise.

Formula

velocity = releases / time_period_weeks

releases
Number of releases shipped
time_period_weeks
Length of measurement period (weeks)

Worked example

With the default values below, Release Velocity Calculator returns Current Release Velocity of 2.75. Change any input above and every figure here is recalculated in your browser.

Inputs used

Releases (Previous Period)accepts 0–1,000,000 releases
8 releases
Releases (Current Period)accepts 0–1,000,000 releases
11 releases
Period Lengthaccepts 0.1–1,000 weeks
4 weeks

Results

Current Release Velocity
2.75 releases/week
Trend
Accelerating
Change vs Previous Period
37.5%
Previous Release Velocity
2.00 releases/week

Step by step

  1. 1Previous velocity: releases ÷ period weeks= 2.00 releases/week
  2. 2Current velocity: releases ÷ period weeks= 2.75 releases/week
  3. 3Change: current − previous= 37.5% (Accelerating)

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

Why normalize to releases per week instead of comparing raw counts?

Comparing raw release counts across periods of different lengths (or with different numbers of working days/holidays) can be misleading — normalizing to a rate makes the comparison meaningful regardless of exact period length.

What's a healthy release velocity trend?

A gently accelerating or stable trend generally reflects a maturing delivery pipeline; a sharply decelerating trend can signal growing technical debt, testing bottlenecks, or an increasingly risk-averse release process worth investigating.

How does this differ from the DORA deployment frequency metric?

Deployment frequency measures a single period's rate against DORA's performance tiers; release velocity specifically tracks the trend between two periods to answer 'are we speeding up or slowing down,' which deployment frequency alone doesn't capture.

Should hotfixes count as releases in this calculation?

Be consistent — if your deployment frequency metric counts all production deployments including hotfixes, use the same definition here, since mixing definitions between periods would create a false trend signal.

Related Calculators

Release Velocity Calculator | Calcrivo