Skip to main content

DORA Using Only PR Data

In scenarios where deployment and incident data are unavailable, Middleware can compute DORA metrics using only PR data. Here’s how each metric is calculated:

Lead Time for Changes​

Lead time is calculated as the time from the first commit to the merge of the PR. Since deployments are not tracked, the merge to deploy time is set to 0. This calculation includes:

  • First Commit to PR Open Time
  • First Response Time
  • Rework Time
  • Merge Time

You can configure workflows to sync for repository deployments or decide whether to use PR merges or actual deployments as the basis for your team’s deployment metrics.

img

Deployment Frequency​

Deployment frequency is determined by the number of PR merges within a specified interval (daily, weekly, or monthly). PR merges are treated as deployments.

Mean Time to Restore (MTTR)​

  • If incident providers are not configured, code repositories can be inferred as incident services.
  • Revert PRs are then treated as incidents. The resolution time is calculated from the merge of the original PR to the merge of the revert PR.
  • Once incident services are mapped, revert PRs are excluded from the calculation.

Change Failure Rate (CFR)​

CFR is calculated as the ratio of failed PRs (PRs with corresponding revert PRs) to the total number of Merged PRs or Deployments within the interval. Revert PRs indicate deployment failures. This approach ensures that teams without deployment and incident integrations can still gain meaningful insights into their development processes.

Middleware’s flexibility ensures that your DORA metrics are as accurate and meaningful as possible, regardless of your unique team structure and workflows. Book a demo to unblock your team!