Flow analytics shifts the focus from sprint commitments to the continuous movement of work through your system. Rather than asking "did we finish what we planned?", flow metrics ask "how fast does work move from start to done, and where does it get stuck?" This perspective is essential for teams moving toward continuous delivery.
Cycle Time Explained
Cycle time is the elapsed calendar time from when a work item is first moved to an "active" state to when it reaches "done". It is the most direct measure of how quickly your team delivers value.
Cycle Time Distribution
Agile Analytics plots cycle time as a scatter chart over time. This reveals outliers (items that took 3× longer than average) and whether your cycle time is stable or trending upward. The 50th and 85th percentile lines are particularly useful: the 85th percentile is a reliable upper bound for SLA commitments.
What Drives Long Cycle Times?
Common causes of long cycle times include:
- Context switching — developers pulled across too many items simultaneously
- Waiting states — items blocked on review, testing, or external dependencies
- Large batch sizes — stories that are too big to complete in a few days
- Unplanned work — bugs and interrupts consuming capacity
Flow Efficiency
Flow efficiency = active time ÷ total elapsed time. It measures the percentage of cycle time where work is actually being worked on (as opposed to waiting). A flow efficiency below 15% is common but signals significant queue waste. World-class teams often achieve 40%+.
- Active time — time spent in states like "In Progress" or "In Review"
- Wait time — time spent in states like "Ready for Dev", "Waiting for Review", "Blocked"
- Improving flow efficiency requires reducing handoff delays, not necessarily working faster
WIP Monitoring
WIP (Work In Progress) is the count of items actively in progress across your team at any given time. Little's Law states: Cycle Time = WIP ÷ Throughput. This means that reducing WIP directly reduces average cycle time without requiring anyone to work faster.
WIP Limits
Agile Analytics lets you configure WIP limit thresholds per column or state. When the current WIP exceeds the limit, the dashboard highlights it in amber or red. Setting WIP limits forces a "stop starting, start finishing" culture.
Aging Work Items
The Aging & Blocked view in Agile Analytics shows every in-progress item color-coded by age relative to your 85th percentile cycle time. Any item older than the 85th percentile is at risk of becoming a statistical outlier and should be reviewed in standup.
Practical Steps to Improve Flow
Implement these practices to see measurable improvements in cycle time and flow efficiency within 2–3 sprints:
- Set a WIP limit of no more than 1.5× team size for the "In Progress" column
- Review aging items daily — anything older than your 85th percentile cycle time needs attention
- Map your workflow states and identify which are active vs. waiting — eliminate unnecessary wait states where possible
- Reduce story size so most items complete within 1–3 days
- Track flow efficiency monthly and celebrate improvements — even moving from 12% to 18% is significant