Standard : Work Item Age (Time in Progress)

Description

Work Item Age measures how long a piece of work has been in progress since it was started but not yet completed. Unlike cycle time, which is measured after an item is done, Work Item Age provides a real-time indicator of potential flow risk and delay.

Tracking item age helps teams spot ageing or stagnating work, limit WIP, and surface issues like scope creep, context switching or hidden blockers.

How to Use

What to Measure

  • Start Point: When the item is moved to an active state (e.g. “In Progress”).
  • Current Time: Now, or end of tracking period.
  • Include all unfinished items still in progress to calculate their age.

Measure individually per item and track:

  • Average and median work item age
  • Maximum (oldest) item age
  • Trends over time and across work types

Formula

Work Item Age = Current Date – Date Work Started

This should be tracked continuously, not retrospectively.

Instrumentation Tips

  • Use workflow tools (e.g. Jira, Azure DevOps) with accurate state transitions.
  • Tag and monitor items that have been in progress longer than a defined threshold (e.g. 5, 10, 15 days).
  • Visualise ageing work in dashboards or board overlays to drive daily attention.

Benchmarks

Benchmarks vary by team and work type. Example guidance:

Work Type Typical Max Age Target
Bugs < 2–3 days
Stories < 5–7 days
Spikes < 3–5 days
Tech Debt Tasks < 7–10 days

Set team-specific thresholds and use them as triggers for discussion, not as rigid rules.

Why It Matters

  • Supports WIP management
    Ageing items often indicate excessive WIP or overloaded teams.

  • Identifies stuck or risky work
    The longer an item is in progress, the more likely it is to become delayed or blocked.

  • Improves flow awareness
    Encourages teams to finish what they start and reduce context switching.

  • Enables proactive intervention
    Provides early signals that allow teams to unblock or re-scope items before they become problems.

Best Practices

  • Visualise work item age on Kanban boards using colour indicators or badges.
  • Set WIP age alerts and review aged items in stand-ups.
  • Use “aging work” views in retrospectives to surface systemic causes.
  • Combine with cycle time and flow efficiency for a full picture of delivery health.

Common Pitfalls

  • Ignoring age until after work is complete, losing the real-time benefit.
  • Failing to distinguish between in-progress and paused or blocked work.
  • Tracking age without clear start state definitions.
  • Treating high age as normal, reducing the metric’s impact over time.

Signals of Success

  • Reduction in average and max work item age over time.
  • Aged work items are proactively addressed in team ceremonies.
  • WIP limits are respected and enforced based on active capacity.
  • Work flows consistently and predictably across sprints or weeks.
  • [[Cycle Time per Work Item Type]]
  • [[Flow Efficiency]]
  • [[Blocked Time per Work Item]]
  • [[WIP per Team or Stream]]

Aligned Industry Research

  • ActionableAgile (Daniel Vacanti)
    Highlights work item age as a real-time flow signal, crucial for detecting flow risks early.

  • Kanban Method (David J. Anderson)
    Promotes visualising work item age to identify aging inventory and manage flow proactively.

  • Flow Metrics for Scrum Teams (ActionableAgile)
    Advises tracking age alongside cycle time to forecast and manage delivery uncertainty.