Outcome Telemetry

Outcome Telemetry records the readings releases are judged by: metrics from your connectors, and signals such as bugs, regressions, incidents, tickets and customer feedback. Each reading shows the release it counts towards.

Connectors

A connector is a named source of readings — a GitHub or Jira count, product analytics, anything you measure. Add one for each key result a release should move, before the release, and name it on the release’s expected signals (see Release Management).

Recording a reading

Choose the connector, the value (a number), and its kind: a metric, or a signal with a type — bug, regression, revert, incident, ticket, feedback or analytics. Optionally give the time it was recorded (never in the future), a note, and the release it counts towards. Without a release, it counts towards the released release whose window it falls in and whose expected signal names its connector.

Where readings go

Readings and connectors are stored on the server and shared with everyone in the studio. Pulling readings automatically from GitHub or Jira is planned; until then they are recorded on this page. The Feedback Loop is where releases are judged against them.