A reference from Weave

Find a term

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

Terms beginning with D

176 terms
  • Deployment frequency definition

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

    DORA and DevOps
  • Deployment gate

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

    DORA and DevOps
  • Deployment guardrail

    Deployment guardrail 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
  • Deployment interval

    Deployment interval 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
  • Deployment marker

    Deployment marker 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
  • Deployment observability

    Deployment observability 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
  • Deployment path

    A deployment path is the sequence of decisions, checks, environments, approvals, and automation through which a software change moves from a validated state to production. It includes the events that release the change and the feedback that confirms or rejects the result.

    DORA and DevOps
  • Deployment pipeline

    Deployment pipeline 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
  • Deployment queue time

    Deployment queue 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
  • Deployment readiness

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

    DORA and DevOps
  • Deployment recovery time

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

    DORA and DevOps
  • Deployment rework

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

    DORA and DevOps
  • Deployment rework rate

    Deployment rework rate is the proportion of deployments that are unplanned and occur in response to a production incident. It describes incident-driven release work, rather than every code edit, reopened ticket, or revised pull request.

    DORA and DevOps
  • Deployment ring

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

    DORA and DevOps
  • Deployment rollback rate

    Deployment rollback rate 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
  • Deployment strategy

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

    DORA and DevOps
  • Deployment success rate

    Deployment success rate 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
  • Deployment verification

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

    DORA and DevOps
  • Deprecation

    Deprecation is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt
  • Design debt

    Design debt is a software maintenance concern describing a condition that can make future changes, verification, operation, or ownership harder. Its practical importance depends on supported behavior, rate of change, and the consequences of delay.

    Code quality and technical debt
  • Design review

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

    Code review
  • Desired state

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

    DORA and DevOps
  • Developer contribution

    Developer contribution is a developer productivity concept that helps teams understand developer contribution in the context of software delivery.

    Developer productivity
  • Developer documentation

    Developer documentation 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
  • Developer effort

    Developer effort is a developer productivity concept that helps teams understand developer effort in the context of software delivery.

    Developer productivity
  • Developer experience

    Developer experience is how developers experience the tools, processes, and organizational conditions involved in doing their work. It includes the ease of understanding a system, obtaining feedback, collaborating, and making progress without unnecessary friction.

    Developer productivity
  • Developer friction

    Developer friction is a developer productivity concept that helps teams understand developer friction in the context of software delivery.

    Developer productivity
  • Developer portal

    Developer portal 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
  • Developer productivity

    Developer productivity describes how effectively developers turn their time, expertise, and tools into useful software outcomes. It includes the quality and impact of the work as well as the conditions that make sustained progress possible.

    Developer productivity
  • Developer productivity change size

    Change size is a developer productivity concept that helps teams understand change size in the context of software delivery.

    Developer productivity
  • Developer productivity decision latency

    Decision latency is a developer productivity concept that helps teams understand decision latency in the context of software delivery.

    Developer productivity
  • Developer productivity deep work

    Deep work is a developer productivity concept that helps teams understand deep work in the context of software delivery.

    Developer productivity
  • Developer productivity flow predictability

    Flow predictability is a developer productivity concept that helps teams understand flow predictability in the context of software delivery.

    Developer productivity
  • Developer productivity flow state

    Flow state is a developer productivity concept that helps teams understand flow state in the context of software delivery.

    Developer productivity
  • Developer productivity focus time

    Focus time is a developer productivity concept that helps teams understand focus time in the context of software delivery.

    Developer productivity
  • Developer productivity forecast confidence

    Forecast confidence is a developer productivity concept that helps teams understand forecast confidence in the context of software delivery.

    Developer productivity
  • Developer productivity handoff delay

    Handoff delay is a developer productivity concept that helps teams understand handoff delay in the context of software delivery.

    Developer productivity
  • Developer productivity knowledge sharing

    Knowledge sharing is a developer productivity concept that helps teams understand knowledge sharing in the context of software delivery.

    Developer productivity
  • Developer productivity sustainable pace

    Sustainable pace is a developer productivity concept that helps teams understand sustainable pace in the context of software delivery.

    Developer productivity
  • Developer productivity task switching

    Task switching is a developer productivity concept that helps teams understand task switching in the context of software delivery.

    Developer productivity
  • Developer productivity throughput forecast

    Throughput forecast is a developer productivity concept that helps teams understand throughput forecast in the context of software delivery.

    Developer productivity
  • Developer self-service

    Developer self-service is the ability for a software team to complete a supported engineering task through a platform or documented workflow without waiting for another team to perform routine steps. It includes clear ownership, safe defaults, and a recovery path when the standard route does not fit.

    Developer productivity
  • Developer velocity

    Developer velocity is the rate at which a software team turns an idea into a reliable result while preserving a sustainable developer experience. It includes delivery flow, quality, feedback speed, and the conditions that help people do effective work.

    Developer productivity
  • Developer workload

    Developer workload is a developer productivity concept that helps teams understand developer workload in the context of software delivery.

    Developer productivity
  • Development set

    Development set is a defined lens for examining AI system behavior with a stated task, evidence, and interpretation rule.

    Evaluations and benchmarks
  • DevOps change management

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

    DORA and DevOps
  • Diagnostic metric

    Diagnostic metric helps explain why a headline outcome changed.

    Engineering analytics
  • Difference in differences

    Difference in differences is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.

    Measurement and experimentation
  • Directed acyclic graph

    Directed acyclic graph is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.

    Measurement and experimentation
  • Directional hypothesis

    Directional hypothesis is a statistical or measurement concept used to describe, compare, or interpret engineering data. Its meaning depends on the unit of analysis, data-generating process, and question being asked.

    Measurement and experimentation