Engineering excellence

Delivery measures from GitHub, shown against the goals the work serves.

“We ship more often than last year. Can we show what that did for the business?”

Outcome reads pull requests and deployments from GitHub and calculates delivery measures by repository. Each can sit on a goal, beside the result it was for.

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.

What you get
  • Delivery measures from GitHubLive

    Deployment frequency and lead time by repository, and change failure rate where failed deployments are reported.

  • Pull request flowLive

    See pull request cycle time and size by repository, and how each has changed.

  • Delivery measures on a goalLive

    Use a delivery measure such as cycle time as a goal's measure, with a target and a date.

  • Goal named in the pull requestLive

    Engineers state the goal once in the pull request description and the link is made for them.

  • Each team's work by weekLive

    Each team sees its own pull requests and tickets week by week, without tagging anything by hand.

  • Pace to targetLive

    See early whether the current rate of improvement reaches the target on time.

Live In the product today. Preview Working, refined with customers.

An example

Kestrel's mortgage platform team sets a goal to halve its lead time.

  1. 01GitHub is connected. Lead time shows as six days, with deployments twice a week.
  2. 02The team sets a target of three days by quarter end. By week seven lead time is four days.
  3. 03The pace line shows a miss of about a fortnight. The engineering lead agrees a smaller batch size.

Kestrel Bank is a fictional example. The figures are calculated by the product.

What you connect
  • GitHub
  • Jira and Atlassian
  • PagerDuty
  • Slack

If a system you rely on is not listed, ask for it. Outcome’s integration builder drafts the connection, and it is offered to you to try before it is switched on. How the agents work

Beside the tools you have

Delivery measures are read from GitHub and judged against your own targets. Time to restore and time to acknowledge are read from PagerDuty, in preview.

See how Outcome compares

Teams see whether delivery is improving, and leaders read it beside the goal it was meant to move.

More in engineering excellence