# Measure the delivery system

Taiga Learning · Worksheet
https://taiga.training/en/lessons/delivery-metrics/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Distinguish delivery performance from code-generation activity.
- Interpret a metric using its event definitions and scope.
- Use measurements to select an improvement rather than rank individuals.

## Exercise
Use the ten-change dataset in this lesson. Define a deployment, a failed change, and a recovery event. Find the longest visible wait and state what would establish its cause. Propose an improvement and a measure that would reveal worse quality.

[Download the fictional timing dataset (CSV)](https://taiga.training/en/worksheets/delivery-metrics-data.csv)

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Measure accepted changes and their consequences. Keep the event definitions, service context, and limits visible when comparing results.

## Sources
- [DORA: Software delivery performance metrics](https://dora.dev/guides/dora-metrics/)
- [Taiga docs: Deployments and metric definitions](https://docs.tai.ga/deliver/deployments/)
- [Google SRE: Implementing SLOs](https://sre.google/workbook/implementing-slos/)

This worksheet supports learning. Completing it does not itself authorize a production change.