⭐️Delivery Metrics

Purpose

Delivery Metrics measure pull request lifecycle timing and stage efficiency. They provide visibility into how long work takes to move from coding to production and where bottlenecks occur.

These metrics evaluate workflow speed, process friction, and handoff delays.

Metrics Included

The following metrics belong to the Delivery family:

• Cycle Time
• Coding Time
• Pickup Time
• Review Time
• Time to Review
• Time to Approve
• Time to Merge
• Deploy Time

These metrics collectively provide a full view of delivery performance across coding, review, merge, and deployment stages.

How These Metrics Work Together

Delivery metrics represent sequential stages of the PR lifecycle:

Coding → Pickup → Review → Deploy

Cycle Time aggregates these stages into total elapsed time. Stage timing metrics isolate bottlenecks within the workflow.

Custom stages extend this model to organization-specific release flows.

Dashboards That Use Delivery Metrics

Delivery metrics appear in:

• Velocity Dashboard
• Time Distribution Dashboard
• Investment Strategy Dashboard
• DORA Dashboard (Lead Time component)

These dashboards combine Delivery metrics with Throughput and Quality metrics to provide contextual insights.

Related Metric Families

Delivery metrics often correlate with:

• Throughput Metrics (volume vs. speed)
• Quality Metrics (review depth vs. review time)
• Reliability & DORA Metrics (lead time and deployment performance)

Configuration Dependencies

Delivery metrics rely on:

• Pull Request lifecycle events
• Accurate stage mapping
• Deployment mapping (if deploy stages are enabled)
• Custom stage configuration (if applicable)

Improper stage configuration may affect metric accuracy.

Troubleshooting

If Delivery metrics appear inconsistent:

• Validate PR lifecycle events are syncing correctly.
• Confirm custom stages are configured as intended.
• Verify deployment mapping for deploy-related metrics.

For detailed troubleshooting guidance, see: Troubleshooting .