Framework · Delivery metrics

DORA and flow measures from GitHub, beside the goals the work serves.

Outcome reads deployment frequency, lead time and pull request cycle time from GitHub, by repository and environment. Change failure rate appears where GitHub reports failed deployments.

In the product
Kestrel Bankdemo data

A mortgage offer in a day, not a fortnight

1 waiting on you · 3 moving · 1 stuck

Reaches no goal

2 moving

Needs you1

Working4

Reaches no goal

In review3

Reaches no goal

Stuck1

Done2

Work moves as people and agents move it. Outcome reads each change from the tools it happened in.

The work people and agents have under way, in rows by the goal it serves. Work that reaches no goal has its own row.

The question

“We track delivery measures already. Can we show what an improvement in them did for the business?”

  • DORA measures

    Deployment frequency and lead time are calculated by repository, and change failure rate where failures are reported.

  • Pull request flow

    Pull request cycle time and size are shown by repository, with how each has changed over the period.

  • A measure on a goal

    A delivery measure can be a goal's measure, with your own target, date and view of pace.

  • Agent and human work

    The share of merged pull requests written by agents is shown, with cycle time beside the human figure.

Read more

Engineering leaders keep the delivery measures they know and show them beside the business result each improvement supports.

Other frameworks OKRs · product operating model · lean portfolio management · TBM and FinOps