Enter Delivery Data
Use the form below to calculate DORA metrics, compare them against targets, and export the report.
Example Data Table
This sample shows how one reporting period flows through the calculator.
| Team | Period Days | Deployments | Failed Deployments | Changes | Total Lead Minutes | Incidents Restored | Total Restore Minutes | Deployments/Week | Lead Hours | Failure Rate | MTTR |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Platform Team | 30 | 24 | 2 | 120 | 86400 | 2 | 180 | 5.60 | 12.00 | 8.33% | 90.00 mins |
Formula Used
The calculator uses the following formulas and compares actual values with custom targets.
- Deployment Frequency per Day = Total Deployments ÷ Period Days
- Deployment Frequency per Week = Deployment Frequency per Day × 7
- Deployment Frequency per 30 Days = Deployment Frequency per Day × 30
- Average Lead Time = Total Lead Time for Changes ÷ Total Changes Delivered
- Change Failure Rate = Failed Deployments ÷ Total Deployments × 100
- Change Success Rate = 100 − Change Failure Rate
- Mean Time to Restore = Total Restore Minutes ÷ Incidents Restored
- Average Changes per Deployment = Total Changes Delivered ÷ Total Deployments
- Overall Target Attainment = Average of the four metric target scores
How to Use This Calculator
Follow these steps to build a consistent delivery performance report.
- Enter the team name, reporting label, and environment.
- Set the number of calendar days in the reporting period.
- Enter total deployments completed during that period.
- Add the number of failed deployments or failed release changes.
- Enter total delivered changes and their combined lead time in minutes.
- Enter restored incidents and the total minutes spent restoring service.
- Set weekly, lead time, failure rate, and restore time targets.
- Press the calculate button to show results above the form.
- Review the table, cards, and graph, then export CSV or PDF.
Frequently Asked Questions
1. What are DORA metrics?
DORA metrics are four delivery measurements: deployment frequency, lead time for changes, change failure rate, and time to restore service. Together, they show delivery speed and operational stability.
2. Why is deployment frequency important?
Deployment frequency shows how often code reaches production. Higher, sustainable frequency often signals smaller batches, smoother release processes, and stronger delivery flow.
3. What does lead time for changes measure?
Lead time measures how long a change takes to move from committed work to live delivery. Lower lead time usually means faster feedback and less waiting.
4. How is change failure rate interpreted?
Change failure rate shows the percentage of deployments that caused incidents, rollbacks, or hotfixes. Lower values usually indicate more reliable releases.
5. What is time to restore service?
Time to restore service measures the average time needed to recover after a deployment-related incident. Faster recovery reduces customer impact and operational stress.
6. Can I use custom targets?
Yes. This calculator compares actual results against your own targets. That makes it useful for teams with different release cadences, service levels, and risk profiles.
7. Should I track by team or by product?
You can do either. Many organizations track both views, because team-level numbers guide improvement work while product-level numbers show customer-facing delivery behavior.
8. Why export CSV and PDF reports?
CSV files help with spreadsheet analysis and dashboards. PDF reports are useful for sharing snapshots with managers, stakeholders, and delivery review meetings.