> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/metrics-and-reports/glossary.md).

# Glossary

{% hint style="info" %}
This page is in progress.
{% endhint %}

## Ticket Terms

<table><thead><tr><th width="235">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Backlog</strong></td><td>time span from ticket creation to an assignment to a contributor</td></tr><tr><td><strong>Pickup</strong></td><td>time spans from assignment to a contributor until its status changes to an in-progress stage</td></tr><tr><td><strong>Resolution</strong></td><td>time span from being in-progress until being marked as resolved/done etc.</td></tr><tr><td><strong>Lead Time</strong></td><td>Lifecycle of a ticket from creation to being done</td></tr><tr><td><strong>Throughput</strong></td><td>Number of items processed in time. E.g. number of tickets closed.</td></tr><tr><td><strong>Velocity</strong></td><td>Same as throughput. Often used in VSM/Flow frameworks.</td></tr><tr><td><strong>Capacity</strong></td><td>Throughput in achieving a goal, e.g., number of tickets successfully resolved in a sprint. Sustained achievable outcomes.</td></tr><tr><td><strong>Overloaded</strong></td><td>Beyond a pre-defined capacity. For instance a contributor has more than a certain healthy number of tasks assigned.</td></tr><tr><td><strong>Sprint Overrun</strong></td><td>Defined per ticket. A ticket overruns a sprint if it is not resolved in the initially assigned sprint.</td></tr><tr><td><strong>Unplanned Work</strong></td><td>Defined per ticket. A ticket is unplanned if it is added to a sprint after the initial sprint start date.</td></tr><tr><td><strong>Slow Response</strong></td><td>Defined per ticket. A ticket that has been assigned but has not been moved to in-progress for more than a pre-defined time.</td></tr><tr><td><strong>Unassigned WIP</strong></td><td>Defined per ticket. A ticket that has been moved to a work-in-progress (WIP) state, but is not assigned to anyone</td></tr><tr><td><strong>Long Running WIP</strong></td><td>Defined per ticket. A ticket that has been moved to an in-progress state, but has not been closed in a pre-defined time.</td></tr></tbody></table>

## Code & Pull Request (PR) Terms

<table><thead><tr><th width="235">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Development</strong></td><td>time from first commit to opening the PR</td></tr><tr><td><strong>Response</strong></td><td>time from opening the PR to start of a review</td></tr><tr><td><strong>Review</strong></td><td>time from first review response to approval of the PR</td></tr><tr><td><strong>Integration</strong></td><td>time from approval of the PR until its merge/closure</td></tr><tr><td><strong>Cycle Time</strong></td><td>Lifecycle of a PR from creation to being merged/closed.</td></tr><tr><td><strong>Throughput</strong></td><td>Number of items processed in time. E.g.: number of PRs merged.</td></tr><tr><td><strong>Velocity</strong></td><td>Same as throughput. Often used in VSM/Flow frameworks.</td></tr><tr><td><strong>Capacity</strong></td><td>Throughput in achieving a goal, e.g., number of PRs reviewed in a sprint. Sustained achievable outcomes.</td></tr><tr><td><strong>Overloaded</strong></td><td>Beyond a pre-defined capacity. For instance a contributor has more than a certain healthy number of PRs open in parallel.</td></tr><tr><td><strong>Non-Productive Work</strong></td><td>Defined per PR. A PR that has been opened but does not make it into the product, i.e., gets closed or abandoned without merging.</td></tr><tr><td><strong>Merged Outside Process</strong></td><td>Defined per PR. A PR is merged without being reviewed or approved.</td></tr><tr><td><strong>Stale</strong></td><td>Defined per PR. A PR has been opened but did not progress from one stage to another in a pre-defined time.</td></tr><tr><td><strong>Long Running WIP</strong></td><td>Defined per PR. A PR that has been opened but not merged in a pre-defined time.</td></tr><tr><td><strong>Risky Change</strong></td><td>A pull request flagged for extra attention because it is unusually large or far-reaching — for example, changing a high number of lines, spanning many commits, or touching many files.</td></tr><tr><td><strong>Complex Review</strong></td><td>A pull request flagged for extra attention because its review involved unusually high effort — for example, a high volume of review comments, multiple review cycles, or several active reviewers.</td></tr><tr><td><strong>New Work</strong></td><td>New code being committed that does not change existing code.</td></tr><tr><td><strong>Rework Own</strong></td><td>Changes a developer makes to recently written code that they originally authored.</td></tr><tr><td><strong>Rework Others</strong></td><td>Changes a developer makes to recently written code that was originally authored by someone else.</td></tr><tr><td><strong>Maintenance code</strong></td><td>Changes to older, established code rather than recently written code.</td></tr></tbody></table>

## DORA Terms

<table><thead><tr><th width="235">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Deployment Frequency</strong></td><td>How often a team successfully deploys to production. Higher frequency indicates smaller, more manageable changes.</td></tr><tr><td><strong>Lead Time for Changes</strong></td><td>Time from code committed to code running in production. Measures the efficiency of the delivery pipeline.</td></tr><tr><td><strong>Change Failure Rate</strong></td><td>Percentage of deployments that require immediate intervention (rollbacks or hotfixes). Measures deployment quality.</td></tr><tr><td><strong>Failed Deployment Recovery Time</strong></td><td>Time from a deployment-caused failure to service restoration. Formerly called Mean Time to Recovery (MTTR). Renamed in 2023 to scope specifically to deployment failures.</td></tr><tr><td><strong>Deployment Rework Rate</strong></td><td>Percentage of deployments that are unplanned fixes for production issues. Introduced as the 5th DORA metric in 2024.</td></tr></tbody></table>