Continuous flow
Also known as Continuous delivery flow, Flow-based delivery
Definition
Continuous flow is a way of managing work in which items are pulled and completed individually or in small increments, with attention to queues and capacity rather than a fixed iteration boundary.
Flow without a calendar reset
Continuous flow does not mean work moves continuously without waiting. It means the system pulls work when capacity and policy allow, rather than treating the end of a sprint as the only completion opportunity. WIP limits and explicit finish rules help keep the stream visible.
A concrete example
An illustrative team finishes a small change on Wednesday, validates it, and releases it that afternoon. A second change enters review when a reviewer becomes available rather than waiting for a Friday batch. The team still has controls, but its queue is not tied to a ceremony date.
Manage the system
Watch arrival rate, throughput, item age, and blocked time. Continuous flow can expose a bottleneck quickly because work does not disappear into a sprint boundary. Use classes of service when urgent or date-bound work needs different handling.
Limitations
Some coordination requires a cadence, and some work has a natural batch. Continuous flow is a management pattern, not a requirement to eliminate planning, release windows, or group decisions.
How this relates to Weave
Weave can help teams inspect delivery timing and change activity across a continuous workflow. It can provide evidence about queues and outcomes, while the team remains responsible for defining its policies and deciding which work is safe to pull next.
Explore Engineering intelligence