Glossary
Common terms and definitions used in Logilica.
Last updated
Common terms and definitions used in Logilica.
Last updated
| Term | Definition |
|---|---|
| Term | Definition |
|---|---|
Backlog
time span from ticket creation to an assignment to a contributor
Pickup
time spans from assignment to a contributor until its status changes to an in-progress stage
Resolution
time span from being in-progress until being marked as resolved/done etc.
Lead Time
Lifecycle of a ticket from creation to being done
Throughput
Number of items processed in time. E.g. number of tickets closed.
Velocity
Same as throughput. Often used in VSM/Flow frameworks.
Capacity
Throughput in achieving a goal, e.g., number of tickets successfully resolved in a sprint. Sustained achievable outcomes.
Overloaded
Beyond a pre-defined capacity. For instance a contributor has more than a certain healthy number of tasks assigned.
Sprint Overrun
Defined per ticket. A ticket overruns a sprint if it is not resolved in the initially assigned sprint.
Unplanned Work
Defined per ticket. A ticket is unplanned if it is added to a sprint after the initial sprint start date.
Slow Response
Defined per ticket. A ticket that has been assigned but has not been moved to in-progress for more than a pre-defined time.
Unassigned WIP
Defined per ticket. A ticket that has been moved to a work-in-progress (WIP) state, but is not assigned to anyone
Long Running WIP
Defined per ticket. A ticket that has been moved to an in-progress state, but has not been closed in a pre-defined time.
Development
time from first commit to opening the PR
Response
time from opening the PR to start of a review
Review
time from first review response to approval of the PR
Integration
time from approval of the PR until its merge/closure
Cycle Time
Lifecycle of a PR from creation to being merged/closed.
Throughput
Number of items processed in time. E.g.: number of PRs merged.
Velocity
Same as throughput. Often used in VSM/Flow frameworks.
Capacity
Throughput in achieving a goal, e.g., number of PRs reviewed in a sprint. Sustained achievable outcomes.
Overloaded
Beyond a pre-defined capacity. For instance a contributor has more than a certain healthy number of PRs open in parallel.
Non-Productive Work
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.
Merged Outside Process
Defined per PR. A PR is merged without being reviewed or approved.
Stale
Defined per PR. A PR has been opened but did not progress from one stage to another in a pre-defined time.
Long Running WIP
Defined per PR. A PR that has been opened but not merged in a pre-defined time.
Risky Change
A PR that meets one of the following criteria:
More than 100 LoC changed, or
The PR contains more than 10 commits, or
The PR touches on more than 10 files.
Complex Review
A PR that meets one of the following criteria:
It attracted more than 10 review comments, or
It went already through more than 1 review cycle, or
It has more than 1 additional reviewer being active on it.
New Work
New code being committed that does not change existing code.
Rework Own
Changes to code less than 3 weeks old, that had been committed by the same developer.
Rework Others
Changes to code less than 3 weeks old, that had been committed by a different developer.
Maintenance code
Changes to code older than 3 weeks.