---
title: Delivery performance
slug: delivery-performance
icon: {"faIcon":"fa-solid fa-bolt"}
docTags: 
createdAt: 2023-03-16T10:08:04.000Z
---

Echoes measures delivery performance using industry standard DORA metrics, made popular by [Accelerate](https://itrevolution.com/product/accelerate/). Like every other measurement in Echoes, delivery performance is evaluated at the team level, and never for an individual.

# Evaluating delivery performance

Echoes leverages the data it collects from your integrations to compute the DORA metrics to the best of its abilities. In the cases where it requires extra information to provide a measurement, Echoes favors exposing ingestion APIs to maximize compatibility with the variety of possible development flows.

- [Lead time](docId\:uaynEgynBWb4HK1HaJkfa) is automatically computed from git activity, *except* for two of its components:
  - The “deployment” phase, which spans from a code change being merged to its deployment, uses the deployments information declared through the [Deployments API](docId:0fW7tnRudG4xpxO9TP1Oq).
  - The “preparation” phase, which spans from a ticket being marked “in-progress” to a first commit, is currently measured for code changes linked to a JIRA or Linear ticket exclusively.

- [Deployment frequency](docId\:Q0KVkm5Fy419jT3lHZSN5) and [Change failure rate](docId\:WuxrT8BhEhFj8Wx_ujms8) use the deployments information declared through the [Deployments API](docId:0fW7tnRudG4xpxO9TP1Oq).

- [Mean time to recovery](docId\:lGfIZtDECxM2tQ2KurlIp) requires *either* incidents information declared through the [Incidents API](docId\:OZAF_nXuGztgEdxNCpLvv) or an integration with an incident management system (e.g., [New Relic](docId:3GVgCkhzjz6VpJP8yXTkb) or [PagerDuty](docId\:PEUPkWaxsrRn5Gtl40yYc)).

Similarly to [alignment](docId\:aO1N6fg6rABN97EOfxwHm), targets can be set for delivery performance.