Flow AnalyticsMarch 2, 2026· 6 min read

Using Aging Work Items to Run Better Standups

Daily standups get much more useful when the team focuses on aging work instead of reciting every ticket. Here is how to use item age as a practical delivery signal inside Azure DevOps.

#aging work items#standup#flow analytics#cycle time#azure devops

Many standups feel informative but not corrective. Everyone gives an update, yet blocked or slow-moving work remains in the system for days. Aging work-item views change that dynamic by putting attention on items whose elapsed time is already telling you they are drifting toward risk.

What Item Age Tells You

Item age is the number of days a work item has remained active without reaching done. It is a live signal, not a historical report.

  • A young item usually needs routine coordination only.
  • Aging items indicate hidden waiting, unclear ownership, or oversized scope.
  • Very old items often become the source of sprint misses and delivery surprises.

Use Percentiles, Not Gut Feel

Agile Analytics compares current item age against your historical cycle-time distribution. That makes conversations more grounded.

  • If an item is older than your median cycle time, it deserves a quick check.
  • If it is older than your 85th percentile, it is statistically at risk and should be actively managed.
  • If several items are crossing the same threshold, the issue is probably systemic rather than individual.

A Better Standup Flow

Try structuring standup around risk instead of round-robin status:

  • Review the oldest in-progress items first.
  • Ask what is preventing completion, not what happened yesterday.
  • Decide whether to swarm, split scope, unblock externally, or pause lower-priority work.
  • Only after risk review should the team cover new work or routine updates.

Signals to Watch Together

Aging becomes even more useful when paired with WIP and blocked-state visibility. Rising age plus rising WIP usually means the team is starting too much. Rising age with flat WIP often means review or dependency queues are slowing completion. Those are different problems and need different responses.

The Outcome You Want

The goal is not a prettier chart. It is shorter feedback loops. When teams consistently act on aging signals, work spends less time waiting, cycle time stabilizes, and standups become one of the fastest places to remove delivery friction.

Need more than a blog explanation?

Flow buyers usually want cycle time and WIP monitoring next. Use the use-case page or go directly to plan comparison.

Related reading