If you coach or manage more than one team, checking aging work-in-progress typically means opening each team's board individually. Multi-Team Aging, new in v3.1.5, consolidates that view: all teams, all aging items, one screen.
What It Shows
The view lists every work item that is currently in progress across all teams in your scope, sorted by age. Colour-coded age bands make it immediately clear which items are approaching or exceeding expected cycle times:
- Green — within expected cycle time for the column
- Amber — approaching the p85 threshold
- Red — exceeded the p85 threshold and at risk of becoming a blocker
Why This Matters for Coaches
Agile coaches and delivery managers often spend the first 20 minutes of their day clicking through boards to find blocked or stalled items. Multi-Team Aging compresses that into a single view. It surfaces the most at-risk work across every team so you can prioritise where to spend your coaching attention before your daily stand-ups begin.
How to Use It in Practice
Multi-Team Aging works best as a morning check or as a standing agenda item in program-level stand-ups. Filter to a specific area path to scope the view to a program or value stream. For each flagged item, click through to the Azure DevOps work item to check the history and determine whether it needs escalation.
Relationship to Other Views
Multi-Team Aging complements the single-team Aging & Blocked view in Flow Analytics. The difference is scope: Aging & Blocked is optimised for a Scrum Master working with one team, while Multi-Team Aging is optimised for a coach or manager who needs the full cross-team picture without switching context.