Backlog aging
Also known as Aged backlog, Backlog age
Definition
Backlog aging is the elapsed time since a work item entered a backlog or became ready for consideration. It shows how long demand has waited before entering active delivery.
Age is a waiting signal
Backlog aging is not the same as cycle time. Cycle time usually begins when work starts and ends when it finishes. Backlog age begins earlier, while the item is waiting for selection, clarification, funding, or capacity. Keeping the clocks separate prevents a queue from disappearing before implementation begins.
A concrete example
Suppose a team has 40 requested improvements. Ten entered the backlog this month, while one has waited 180 days for a decision. The old item may be strategically important, obsolete, or underspecified. Its age is a prompt to make a decision, not evidence that it should automatically jump ahead.
Use age bands
Group items into useful ranges such as under 30 days, 30 to 90 days, and over 90 days. Review the oldest examples and the reasons they remain. A shrinking backlog with rising age can indicate that easy items are being removed while difficult decisions remain.
Limitations
Age depends on the chosen start event and on whether the backlog contains ideas, commitments, or ready work. Never compare age across teams without aligning those definitions and accounting for work intentionally parked.
How this relates to Weave
Weave can help teams examine delivery activity and identify patterns around work that remains open for a long time. That evidence can inform backlog conversations, but product planning records are still needed to explain priority, expiration, and intentionally deferred work.
Explore Engineering intelligence