A reference from Weave

Engineering & AI glossary

Understand the metrics, models, and methods behind modern engineering. Clear definitions, practical examples, and a closer look at what the numbers actually mean.

All terms

2,008 terms

  • Review participation

    Review participation is a developer productivity concept that helps teams understand review participation in the context of software delivery.

    Developer productivity

  • Review plan

    Review plan is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review priority

    Review priority is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review quality

    Review quality is a developer productivity concept that helps teams understand review quality in the context of software delivery.

    Developer productivity

  • Review queue

    A review queue is unfinished change work awaiting review activity or a review decision. Its depth and age reveal demand on reviewers and the delay between implementation and the next delivery step.

    Flow and capacity planning

  • Review queue age

    Review queue age is the time that pending review work has remained without the next required action.

    Code review

  • Review queue depth

    Review queue depth measures the number of pending review items at a point in time or across a defined workflow stage.

    Code review

  • Review queue pressure

    Review queue pressure is the condition in which pending review work consumes more capacity than the responsible reviewers can sustainably provide.

    Code review

  • Review rejection

    Review rejection is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review rejection rate

    Review rejection rate is the share of submitted changes that are declined, abandoned, or sent back rather than accepted in their current form.

    Code review

  • Review reopen rate

    Review reopen rate is the share of closed review requests that become active again for additional changes or decisions.

    Code review

  • Review request

    Review request is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review response time

    Review response time measures how long a reviewer or author takes to respond to the next actionable event in a review conversation.

    Code review

  • Review responsiveness

    Review responsiveness is a developer productivity concept that helps teams understand review responsiveness in the context of software delivery.

    Developer productivity

  • Review rework

    Review rework is the author effort or change volume produced in response to review feedback before a proposed change is accepted.

    Code review

  • Review scope

    Review scope is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review service level expectation

    A review service level expectation is a probabilistic statement about how long a defined class of review requests usually takes.

    Code review

  • Review signal-to-noise ratio

    Review signal-to-noise ratio compares useful, actionable review feedback with comments that are irrelevant, duplicated, or purely cosmetic.

    Code review

  • Review SLE

    Review service-level expectation is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review state

    Review state is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Review turnaround time

    Review turnaround time is the elapsed duration from a review request to a defined completion point, such as approval or final feedback.

    Code review

  • Review wait

    Review wait is the queue portion of a change's review interval. It excludes the time spent actively reviewing when those boundaries can be identified.

    Flow and capacity planning

  • Review wait time

    Review wait time is the portion of a change's lifecycle spent waiting for a reviewer, response, or approval rather than receiving active feedback.

    Code review

  • Reviewable change

    Reviewable change is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer

    Reviewer is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer assignment

    Reviewer assignment is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer availability

    Reviewer availability is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer diversity

    Reviewer diversity is the range of technical perspectives, system familiarity, and lived experience represented in review decisions.

    Code review

  • Reviewer expertise

    Reviewer expertise is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer load

    Reviewer load is the amount and complexity of review work assigned to or completed by an individual or group.

    Code review

  • Reviewer rotation

    Reviewer rotation is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reviewer specialization

    Reviewer specialization is the concentration of review responsibility in people with particular domain, security, or system expertise.

    Code review

  • Revision cycle

    Revision cycle is a practical concept in a pull-request workflow that shapes how people examine, discuss, own, or integrate a proposed change.

    Code review

  • Reward model

    Reward model is a language-model concept about mechanism and information flow. It names a mechanism, representation, training practice, or operational behavior that can change how an AI system processes input and produces output.

    LLM fundamentals

  • Rework avoidance

    Rework avoidance is a developer productivity concept that helps teams understand rework avoidance in the context of software delivery.

    Developer productivity

  • Rework burden

    Rework burden is a developer productivity concept that helps teams understand rework burden in the context of software delivery.

    Developer productivity

  • Rework rate

    Rework rate is the proportion of work that must be repeated or revised because the earlier result was incomplete, incorrect, or no longer suitable. Its calculation depends on the work unit and the evidence used to identify rework.

    Code quality and technical debt

  • RICE scoring

    RICE scoring is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.

    Flow and capacity planning

  • Risk-based testing

    Risk-based testing is a software testing or test-design practice used to gather evidence about a defined risk, behavior, boundary, or operating condition. It makes the question under test explicit, identifies the inputs and observations that matter, and gives a team a repeatable basis for deciding whether the result is acceptable.

    Code quality and technical debt

  • Roadmap alignment

    Roadmap alignment is a way to organize, support, or evaluate software work so that teams can make useful progress with less avoidable friction. It is most valuable when connected to a concrete outcome and the local conditions of the team using it.

    Developer productivity

  • Roadmap capacity

    Roadmap capacity is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.

    Flow and capacity planning

  • Roadmap planning

    Roadmap planning is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work.

    Flow and capacity planning

  • Roll-forward

    Roll-forward is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Rollback

    Rollback is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Rollback frequency

    Rollback frequency is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Rollback time

    Rollback time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Rolling average

    Rolling average smooths a moving window while retaining recency.

    Engineering analytics

  • Rolling deployment

    Rolling deployment is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.

    DORA and DevOps

  • Rolling release

    Rolling release is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.

    DORA and DevOps

  • Rollout marker

    Rollout marker is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.

    DORA and DevOps