DORA & Flow Metrics

Time in Status shows how long issues sit in each workflow status, so you can find bottlenecks fast. Here is what it is, how it is measured in Jira, and how to use it.

Cycle time measures how long work actually takes once it starts. Here is what it is, how it is calculated in Jira, and how to use it to remove blockers and speed delivery.

The say/do ratio compares what a team commits to with what it delivers. Here is what planning accuracy is, how to measure it in Jira, and what a healthy ratio looks like.

System stability measures how predictable your delivery is by tracking throughput variance. Here is what it is, how it is calculated in Jira, and how to read it.

Work type distribution shows how your team’s effort splits across features, bugs and technical debt. Here is what it is, how it is measured in Jira, and how to use it.

Work in progress (WIP), or flow load, is the flow metric most under your control and the fastest lever for faster delivery. Here is how to measure and limit it in Jira.

Throughput counts what your team actually finishes each period. Here is what it is, how it is measured in Jira, and how to use it for estimation-free forecasting.

Lead time measures the total wait your customer experiences, from request to delivery. Here is what it is, how it is measured in Jira, and how to use it to deliver value faster.

Cycle time, lead time, and DORA’s lead time for changes are three different clocks. Here’s the difference, with a worked Jira example.

Lead time for changes is a core DORA metric — commit to production. What it means, what counts as good, and how to measure it in Jira.