Introduction
Velocity tells you how much work a team got through last sprint. Flow metrics tell you whether the underlying system is healthy — how long things sit in queues, where work piles up, when delivery is becoming more or less predictable. For teams that want to forecast honestly without over-promising, flow is the foundation.
Forecasting is the other half of the same discipline. Once a team can measure flow, it can project: how likely is it that this work finishes by this date, given how the system has actually been behaving? Done right, that produces grounded conversations with stakeholders instead of hopeful guesses dressed up as commitments.
Topics
Kanban Board Patterns
Column structures, ready queues, and explicit policies that turn a board from a task tracker into a real workflow model.
Read →Swimlanes & Classes of Service
Visualizing different types of work — standard, expedite, fixed-date, intangible — so each gets the treatment it actually needs.
Read →WIP Limits & Buffers
Caps on how much work can be in flight at once. The single most reliable lever for shorter cycle time and better focus.
Read →Cumulative Flow Diagram (CFD)
The visualization that shows arrival rate, work in progress, and throughput on one chart — and exposes batching, bottlenecks, and stalls instantly.
Read →Lead Time vs. Cycle Time
Two related but different measures: how long since the work was requested, and how long since the team actually started it.
Read →Flow Efficiency Metrics
The ratio of active work time to total elapsed time. Often 15%; sometimes 5%. Always uncomfortable when you measure it.
Read →Velocity & Throughput
Story points completed per sprint, or items completed per period. Useful inputs for forecasting when used carefully.
Read →Capacity Planning
Forecasting how much the team can do based on historical capacity rather than aspirational availability.
Read →Burn-Up Charts
Tracking work completed against total scope, with scope shown explicitly so changes don't quietly distort the picture.
Read →Burn-Down Charts
The classic sprint-progress visualization. Useful inside a sprint, misleading when used for release planning.
Read →Process Mapping
Laying out the actual steps work moves through — including the waits, handoffs, and re-work that nobody usually counts.
Read →Value Stream Mapping
A lean technique for mapping end-to-end flow from customer request to delivered value, with explicit measurement of waste.
Read →Monte Carlo Forecasting
Probabilistic delivery forecasts built from the team's actual throughput history. Replaces "when will it be done" with "85% confidence by".
Read →Cone of Uncertainty
A reminder that early estimates carry orders of magnitude more uncertainty than late ones — and a tool for communicating that to stakeholders.
Read →What to Measure First
The simplest place to start is a count and a clock: how many items the team finishes per week, and how long each took from start to done. With a few weeks of that data, the team can forecast with rough confidence. Add WIP limits and a board that reflects the real workflow, and cycle time will usually start dropping on its own as the team stops thrashing.
Avoid the temptation to instrument everything at once. The point of flow metrics is to surface specific decisions: where to add a buffer, when to push back on scope, whether to swarm or split. Pick the metric that answers a question the team actually has, and ignore the rest until they earn their place.
Back to Hubs