Purpose and scope
What this dashboard measures
Summarize work-item ages and flag items beyond an entered threshold.
Items and ages and Stale threshold days feed the secondary measures beneath the Kanban WIP Age Tracker headline; Store Stale threshold days in its entered unit for comparison.
Instructions
How to use this calculator
Define Items and ages and Stale threshold days from the Kanban WIP Age Tracker supplied schedule, then store Stale threshold days in their recorded units.
- Define Items and ages and Stale threshold days from one Kanban WIP Age Tracker reporting period.
- Define Stale threshold days without changing the Stale threshold days unit.
- Assemble the Kanban WIP Age Tracker and reconcile its headline with secondary measures.
Interpretation
Interpreting the headline metric
Age highlights flow risk but does not prove that an item is blocked or incorrectly prioritized.
Verify Items and ages and Stale threshold days beside the Kanban WIP Age Tracker headline; Stale threshold days reveals rounding across the secondary measures.
Pair this Kanban WIP Age Tracker result with the Agile Cycle-Time Percentile Forecaster when you also need to use historical cycle times to forecast completion at a selected percentile.
Calculation
Method used
Entered item ages are compared with a stale threshold and summarized by average, oldest, and flagged count.
The Kanban WIP Age Tracker evaluates Items and ages and Stale threshold days separately; store Stale threshold days visible outside any percentage, rate, or total.
Calculation method last reviewed: June 21, 2026.
Worked scenario
Example calculation
Reconcile Stale threshold days with the Kanban WIP Age Tracker secondary measures before judging the Stale threshold days headline scale or units.
Visual audit
Reading the supporting metrics
The Kanban WIP Age Tracker dashboard places secondary measures beside Items and ages and Stale threshold days. Verify Stale threshold days in its original unit before accepting the secondary measures or headline status.
Boundaries
Important edge cases and limitations
Age alone does not reveal progress, dependency status, priority, or whether an item is intentionally paused.
Alter Stale threshold days in the Kanban WIP Age Tracker before reading the secondary measures or headline.
Input audit
Checklist for this calculation
- Verify the Kanban WIP Age Tracker period and Items and ages and Stale threshold days units.
- Reconcile Stale threshold days with the Kanban WIP Age Tracker secondary measures.
- Assemble a fresh Kanban WIP Age Tracker after any Stale threshold days alter.
Practical use
Recommended workflow
Review the oldest items with owners and record whether waiting, active work, or an external dependency explains the age.
A useful follow-up is the Sprint Burndown Finish-Date Forecaster, which can project when remaining sprint work will finish at the observed delivery rate. To examine an adjacent timing question, use the Critical Path Timeline Calculator to find the longest dependent task chain and earliest project completion.
Questions
Frequently asked questions
Should every item above the threshold be expedited?
No. The threshold starts a review; priority and service class determine the appropriate action.
What context should accompany Items and ages in the
Reconcile Items and ages with Stale threshold days inside the Kanban WIP Age Tracker reporting basis. Store the Stale threshold days unit aligned with the Items and ages period before reading the headline.
Does Stale threshold days alter every part of the kanban wip age tracker result?
Store Items and ages and Stale threshold days unchanged and alter Stale threshold days once in the Kanban WIP Age Tracker. Reconcile the Stale threshold days component with secondary measures to identify a proportional or threshold effect.