Many standups go round the room and still leave stuck work stuck. Everyone reports, nobody changes plans, and the item that has been "nearly done" for eight days stays nearly done. A work item aging chart fixes the order of the conversation. It puts the items that are already running long at the top, before anyone talks about what they did yesterday.
What a work item aging chart shows
An aging chart plots only work that is in progress right now. Each dot is one item. Its position across the chart is the workflow stage it is in, and its height is how many days it has been in flight. Finished work does not appear as dots. It is used for something else: the percentile lines that tell you how long work normally takes. Item age is a live signal. Cycle time tells you how long finished items took. Age tells you which unfinished items are on course to become your next slow ones, while there is still time to act.
- A young item low on the chart usually needs nothing beyond routine coordination.
- An item above the line where half of your past work had finished is worth a question.
- An item above the line where 85% of your past work had finished is already slower than most of what the team has delivered. Treat it as at risk.
Read it against percentiles, not gut feel
Percentile lines turn "this feels slow" into a number the team agrees on. The p50 line is the age at which half of the team’s recently completed items had finished. The p85 line is where 85% had. Use the team’s own history, not a target someone set, because the point is to compare work with how this team actually delivers.
- One item above p85: talk about that item.
- Several items above p85 in the same stage: that stage is probably the problem, not the people.
- Many items between p50 and p85: the team may be starting too much at once, and everything is moving slowly.
Run the standup from the oldest item down
Try this order for a week and compare it with round-robin updates:
- Open the aging chart and start with the oldest item, not the first name on the list.
- For each item above p85, ask what is preventing completion and who can remove it today.
- Decide one action per at-risk item: swarm on it, split it, escalate the dependency, or stop something else to make room.
- Look at blocked items next, and agree who owns each unblock and by when.
- Only then cover new work and routine updates, if there is time.
Aging, WIP and blocked work together
Age means more when you read it next to how much is in progress. Rising age with rising WIP usually means the team is starting more than it finishes. Rising age with flat WIP often means work is waiting in review, test or on another team. Those are different problems with different fixes: the first needs a stop-starting agreement, the second needs attention on the waiting stage. Blocked items need their own look, because a blocked item ages without anyone working on it, and the team stops seeing it after a few days.
Azure DevOps on its own
The standard Azure DevOps widget catalog does not include a work item aging chart. You can get part of the way with a work item query: in-progress items sorted by State Change Date, oldest first, shown as a query tile or a list. That tells you how long each item has sat in its current state. It does not add up time across stages, and it has no percentile lines, so you have to decide yourself what "too old" means.
The aging chart in Agile Analytics
In the Agile Analytics hub, the chart is under Aging & Blocked in the Health group of the navigation, titled Aging Chart. It covers the team’s active sprint, one team at a time. The columns across the chart are the team’s own in-flight states in board order, so the chart looks like the board people already know. The height of each dot is its days in flow: every day it has spent in a workflow stage since it left New, added up across stages, so moving from In Progress to Review does not reset the clock. If an item was reopened, the time it sat in Done is not counted.
- The p50 and p85 lines come from items the team completed in its last six sprints. Dots are green below p50, amber from p50 and red from p85. A team with no completed history yet gets fixed bands of 0 to 3, 4 to 6 and 7 or more days.
- Weekends are excluded by default, using the team’s working days in Azure DevOps. The Weekends control switches between Exclude Weekends and Include Weekends.
- Below the chart, every item in flight is listed and ranked by urgency, with chips such as "over p50" and "3d over p85". Each row also shows the days in the current stage, marked "here".
- Hover a dot for the item’s title, days in flow and days in its current stage. Click a dot, or Open ↗ on a row, to open the work item in Azure DevOps.
- Aging Trend by Sprint shows the average age in each state across recent sprints, which helps you tell a bad week from a pattern.
How blocked items are found
The extension looks for several blocked signals: a yes/no Blocked field, if your organisation has chosen one in Configuration; a state whose name says blocked or on hold; and a tag such as blocked, impediment or on hold. Extra tags and states can be added in Configuration under Blocked signals. Items that match get a ring around their dot and a ⛔ Blocked chip on their row. The Blocked Items pill lists them on their own with the reason, such as Blocked tag or Blocked state. It also lists items marked Stalled, meaning they have sat in their current stage for at least a set number of days (5 by default). Stalled items get no ring on the chart, because their height already shows they are old.
Aging across several teams
If you coach or manage more than one team, opening each team’s chart before the standups begin takes a while. The Multi-Team Aging view, under Agile Coach in the navigation, puts the teams side by side. Pick teams from a project, or across projects, and it shows totals for Aging Items, Stale Items, Blocked Items and Teams At Risk. Teams are sorted into Act Now, Watch and Healthy, and a table lists the oldest items across the selected teams with their team, state, age and how long each has been stuck.
- Standup Mode switches the view to the at-risk teams in a compact layout, which suits a short programme-level standup.
- The filter narrows the list to At Risk, Stale > 0 or Blocked > 0 teams.
- Age in this view is the days an item has spent in its current stage, counted in calendar days, and an item counts as blocked when it has not changed state for longer than the Stale / Blocked Threshold (5 days by default). That is simpler than the single-team chart, so use it to choose which team to look at, then open that team’s Aging Chart for the detail.
What changes when teams act on age
The goal is shorter waits, not a nicer chart. Teams that start each standup from the oldest item tend to find stuck work days earlier, split large items sooner and leave fewer items running past the sprint end. If the p85 line drops over a few sprints, the habit is working.
Related: Azure DevOps WIP monitoring · Cycle time and WIP explained · How to read a cumulative flow diagram · What belongs on a sprint health dashboard