Standard : Work Item Age

Description

Work Item Age is the amount of time that a work item has been in progress, measured from when it started to the current moment. Unlike cycle time, which is only calculated after completion, work item age gives you a real-time view of how long in-flight work has been open.

Tracking work item age helps teams spot ageing or forgotten work, surface blockers, and assess flow health. It provides early signals of delivery risk and unbalanced WIP.

How to Use

What to Measure

  • The elapsed time since a work item was started (entered an “in progress” state).
  • Aggregate age across all current WIP to find bottlenecks or stuck work.
  • Track max, min, and average work item age per workflow, service, or team.

Formula

Work Item Age = Current Time – Start Time of the Work Item

You can also track:

  • Max Work Item Age: Longest ageing item in the system.
  • Average Work Item Age: Across all WIP items at any given point.

Instrumentation Tips

  • Use your delivery board timestamps or tool APIs to extract item start times.
  • Label and monitor blocked or paused work separately.
  • Visualise age trends with charts (e.g. ageing WIP, scatter plots, or control charts).
  • Use alerts for items that exceed threshold durations.

Why It Matters

  • Highlights delivery friction: Aged items often signal complexity, blockers, or unclear ownership.
  • Reduces cycle time: Stale WIP can drag down flow predictability and throughput.
  • Improves flow control: Teams learn when to swarm, split, or reprioritise stuck work.
  • Supports continuous improvement: Tracking ageing items exposes process waste over time.

Best Practices

  • Discuss the oldest work items daily during stand-ups.
  • Track and visualise ageing alongside WIP and cycle time.
  • Apply WIP limits to reduce the number of concurrent items.
  • Swarm on oldest items or explicitly pause them if blocked.
  • Use retrospectives to reflect on causes of prolonged work item age.

Common Pitfalls

  • Only measuring after work is complete, losing real-time visibility.
  • Letting stale work pile up due to multitasking or unclear priorities.
  • Ignoring hidden blockers like waiting on approvals or external teams.
  • Misclassifying work start (e.g. tickets opened early but not actively worked).

Signals of Success

  • Aged WIP is minimal and addressed proactively.
  • Teams can articulate why an item is ageing and what is being done about it.
  • Less rework due to fresher context and reduced context switching.
  • Flow metrics such as cycle time improve over time with fewer long-lived items.
  • [[Flow Efficiency]]
  • [[Cycle Time]]
  • [[Blocked Work Age]]
  • [[Time in Queue]]
  • [[Throughput]]