Skip to main content

Inserisci i dati del team

1 Deployment Frequency
2 Lead Time for Changes

Ore dal commit in produzione alla disponibilita in produzione. Inserisci piu valori separati da virgola.

3 Change Failure Rate
4 Mean Time to Restore (MTTR)

Ore necessarie per ripristinare il servizio dopo un incidente. Inserisci piu valori separati da virgola.

Classificazione DORA

Livello ComplessivoMedium
Deployment Frequency High
2.8x/settimana
12 deploy in 30 giorni = 0.400 deploy/giorno
Elite: multipli/giorno | High: giornaliero | Medium: settimanale | Low: mensile
Lead Time for Changes Medium
1.2 giorni
Media di 5 campioni: 27.6 ore
Elite: < 1 ora | High: < 1 giorno | Medium: < 1 settimana | Low: < 6 mesi
Change Failure Rate High
10.0%
2 falliti su 20 deploy totali
Elite/High: 0-15% | Medium: 16-30% | Low: > 30%
Mean Time to Restore High
2.0 ore
Media di 4 incidenti: 2.0 ore
Elite: < 1 ora | High: < 1 giorno | Medium: < 1 settimana | Low: > 1 mese

Benchmark DORA 2024 (Google)

MetricaEliteHighMediumLow
Deployment FrequencyMultipli/giorno1/giorno - 1/settimana1/settimana - 1/mese< 1/mese
Lead Time for Changes< 1 ora1 ora - 1 giorno1 giorno - 1 settimana> 1 settimana
Change Failure Rate0-5%6-15%16-30%> 30%
MTTR< 1 ora1 ora - 1 giorno1 giorno - 1 settimana> 1 settimana

Fonte: Accelerate State of DevOps Report 2024, Google DORA Research Program. Il livello complessivo e determinato dalla metrica peggiore (principio del minimo).

Come utilizzare DORA Metrics Calculator

Insert deployment and lead time data

Indicate deployment number and observed period (Deployment Frequency), then list the lead times in hours for the last releases, separated by commas.

Insert failed deployments and recovery times

Indicate how many deployments have caused a failure, out of the total, along with the list of recovery times per hour (MTTR), separated by comma.

Read classification for each metric

Calculation is instantaneous: every metric is classified as Elite, High, Medium or Low according to the Google DORA benchmarks with calculated value and reference benchmark.

Verify overall level and copy report

Team overall level corresponds to the worst metric among the 4 (minimum principle). Use "Copy results" to export the textual report.

Suggerimenti

  • Update data periodically (e.g., every sprint or every month) to track the team's trend over time, not just a one-time snapshot.
  • If one metric pulls the overall level down, focus on improving that first before optimizing others in Elite or High.
  • Use Change Failure Rate with MTTR to understand if the issue and quality of releases or response time to incidents are different areas for improvement.

Domande frequenti

What are the four DORA metrics?

Metrics defined by the DORA Research Program at Google to measure DevOps team performance: Deployment Frequency (how often deployments are released), Lead Time for Changes (time from commit to production), Change Failure Rate (percentage of deployments causing incidents) and MTTR, Mean Time to Restore (average time to restore after an incident).

How is overall level determined (Elite/High/Medium/Low)?

The calculator applies the principle of minimum: the overall level of the team corresponds to the worst among the four individual classifications. For example, if three metrics are Elite but the Change Failure Rate and Low, the overall level is Low.

Where do the Elite/High/Medium/Low benchmarks come from?

Accelerate State of DevOps from Google's DORA Research Program, which has been collecting data from thousands of teams since 2014 to define reference thresholds for each metric (e.g. Elite: lead time under 1 hour, Low: lead time over 6 months).

How do I enter lead time and MTTR if I only have a few samples?

Just one value in hours is enough, but more samples (separated by comma or space) will better represent the team's trend instead of a single unusual event. Ideally use the last 5-10 deployments or incidents.

Are my data saved or sent to a server?

No, calculations are performed entirely in the browser using a reactive formula: no data entered is sent or stored on an external server.