Flow metrics tools measure how work moves through a team or value stream, using the start and finish dates your tracker already records. They answer two everyday questions: how long does a typical item take, and when will this batch of work be done?
Showing 3 of 3 tools
Flow metrics & Monte Carlo
Flow analytics from 55 Degrees offering cycle-time scatterplots, aging WIP, CFDs and Monte Carlo forecasts for Jira and Azure DevOps.
Open-source Jira reports
Free Ruby gem that extracts Jira data into HTML reports covering CFDs, cycle-time histograms, throughput and stalled work.
Kanban analytics
Kanban analytics dashboard that pulls board data from Jira, Azure DevOps, Trello and Asana to chart flow and forecast delivery.
The basics
Flow metrics tools read the history of a kanban or issue board and turn it into measures of flow. Most connect to an existing tracker rather than replacing it.
The Kanban Guide names four flow metrics as the minimum: work in progress, throughput, work item age and cycle time. Most tools add charts such as cycle time scatterplots and cumulative flow diagrams.
Many also forecast delivery dates with Monte Carlo simulation. It replays past throughput many times to show a range of likely outcomes, rather than a single date.
A spreadsheet can track start and finish dates for each item and compute cycle time and throughput. That is enough to learn the metrics on one team.
Dedicated tools help when you want work item age at the daily standup, percentile-based forecasts, or the same view across many boards. The Little's Law calculator shows how WIP, throughput and cycle time link.
The routine it supports
How the listed tools are priced
The term flow metrics is used in several frameworks, and they do not use the same list. The Kanban Guide names work in progress, throughput, work item age and cycle time. Mik Kersten's Flow Framework uses flow velocity, flow time, flow load, flow efficiency and flow distribution.
The Scaled Agile Framework adopts the Flow Framework measures and adds flow predictability. Before you choose a tool, decide which set you want to report, because some tools follow one framework closely. The Little's Law calculator shows how the core measures relate.
DORA metrics come from the DevOps Research and Assessment program and measure software delivery performance, such as deployment frequency and lead time for changes. They describe the path from code commit to production.
Flow metrics cover a wider span: from the moment work starts, or is requested, to the moment it is done, whatever kind of work it is. Teams that build software often track both. Some flow metrics tools also read data from code repositories and pipelines, so check which sources a tool connects to.
A useful flow metrics dashboard shows ageing work in progress for the daily standup, a cycle time scatterplot with percentile lines, a throughput run chart and a cumulative flow diagram.
Forecasting views sit on top of those charts. A Monte Carlo forecast reads your throughput history to give a range of dates, each with a probability. Keep the dashboard short enough that the team looks at it.
Buying guide
Who it's for: Delivery leads, agile coaches and managers who are asked "when will it be done?" and want to answer with data rather than estimates.
Clean data connections
Reliable connectors to the work-tracking tool you already use, with control over which statuses count as started and finished.
Cycle time scatterplots
Percentile lines (50th, 85th, 95th) rather than averages, so you can make commitments with known confidence.
Monte Carlo forecasting
"When will these 40 items be done?" and "How many items by this date?" answered as probabilities, based on your real throughput.
Aging work in progress
A view of items that have been in progress longer than usual, so you can act before they become late.
Before you choose
FAQ
Sources
Written by the lean-stack editors following our methodology. Updated October 3, 2026.
For vendors
Submit it for review. Every tool is checked against our listing criteria and researched from public sources. Approved tools join their category in the next published batch.
