A reference from Weave

Find a term

Make sense of queues, work in progress, forecasting, and team capacity. These concepts explain why a busy team can still struggle to finish work.

Terms beginning with D

13 terms

  • Definition of done

    A definition of done is an explicit policy for the conditions a work item must satisfy before it is considered complete. It can include implementation, review, testing, documentation, security, and release requirements.

    Flow and capacity planning

  • Delivery age

    Delivery age is the time since a work item crossed a stated delivery start boundary while remaining unfinished. It is an active-work signal for intervention and forecasting.

    Flow and capacity planning

  • Delivery forecast

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

    Flow and capacity planning

  • Delivery queue

    A delivery queue is unfinished work that has reached a downstream delivery boundary but is waiting for capacity, approval, environment, or a release decision. It makes post-implementation accumulation visible.

    Flow and capacity planning

  • Demand shaping

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

    Flow and capacity planning

  • Demand-capacity ratio

    A demand-capacity ratio compares a defined arrival rate or committed workload with the corresponding capacity or throughput of a delivery system. A ratio above one signals pressure under the stated assumptions, not a diagnosis by itself.

    Flow and capacity planning

  • Dependency constraint

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

    Flow and capacity planning

  • Dependency lead time

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

    Flow and capacity planning

  • Dependency mapping

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

    Flow and capacity planning

  • Dependency resolution time

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

    Flow and capacity planning

  • Dependency risk

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

    Flow and capacity planning

  • Dependency wait

    Dependency wait is the elapsed period caused by a required input or action outside the item's current processing step. It is a specific form of queue or blocked time.

    Flow and capacity planning

  • Downstream dependency

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

    Flow and capacity planning