Lead Time for Changes
Lead Time for Changes: Time from code commit to production deployment.
Formula
Lead Time = Median of (Deploy time - Commit time)Computable definition
The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.
(median(field.deploy_date - field.committed_at)) * 24Unit: hours
Notes: Median of deploy time minus commit time.
Data requirements
Grain: Per event · Frequency: Per deploy · Aggregation: event · Staged: no · Main source: CI/CD.
| Field | Dataset | Type |
|---|---|---|
committed_at | deployment | timestamp |
deploy_date | deployment | timestamp |
Example SQL (Postgres)
SELECT ((SELECT PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY (EXTRACT(EPOCH FROM (deploy_date - committed_at)) / 86400.0)) FROM deployment WHERE deploy_date >= :period_start AND deploy_date < (:period_end + INTERVAL '1 day')) * 24) AS lead_time_for_changes From an agent: with the GASP MCP server, call
lookup_metric({ "name": "Lead Time for Changes" }) or generate_query({ "metric": "Lead Time for Changes", "adapter": "<your adapter JSON>" }).
Benchmarks
- Elite: Less than 1 day
- High: 1 day to 1 week
- Medium: 1 week to 1 month
- Low: 1 month to 6 months
What It Tells You
Development and release pipeline efficiency.