Delivery performance

echoes measures delivery performance using industry standard dora metrics, made popular by 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 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 docid 0fw7tnrudg4xpxo9tp1oq mean time to recovery docid\ lgfiztdecxm2tq2kurlip requires either incidents information declared through the incidents 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