Sprint Capacity
How many person-days does this team actually have for its current sprint? The point of this page is the subtraction — starting from every team member's raw working days, then taking away holidays, part-time allocation, and team-wide days off.
What you see
- The sprint's name (there is no sprint selector on this page — see Known limits).
- A "Person-days available" stat card, with the detail "{people} people · {days} working days in the sprint." Clicking it opens every item in the sprint.
- Alert strips, shown only when relevant: team-wide days off recorded for the sprint; a note that Monday–Friday was assumed because the team never configured its working days; and a note that nobody has hours configured in Azure DevOps, so everyone is counted as a full day per working day.
- A table of team members: Team member, Hours/day, Days off, Person-days. Each member's name is clickable and opens their own items.
- An "Unassigned (N)" row for items with no assignee, when any exist.
How we calculate it
Capacity comes entirely from Azure DevOps' own iteration Capacity settings — per-person hours per day and days off, the team's own days-off calendar, and the team's configured working-day pattern. Agile Gauge does not maintain a separate capacity system.
- Working days
- An inclusive count of calendar days in the sprint that fall on one of the team's configured working days. If the team never configured a working-day pattern, Monday–Friday is assumed, and the page discloses that it's an assumption rather than a real setting.
- Team days off
- The team's recorded days-off ranges, clamped to the sprint window, counting only the working days inside those ranges.
- The "standard day"
- The largest per-person hours-per-day figure configured anywhere on the team. Everyone else's hours are weighted against that standard — a half-day (say, 4 hours against an 8-hour standard) counts as 0.5 of a day.
- If nobody has configured hours at all
- Every person is weighted at 1.0 — one full day counted per working day, unweighted — since there's nothing to weight against.
- Per-person available days
- Working days, minus team days off, minus that person's own days off, floored at zero.
- Per-person person-days
- Available days × that person's weight.
- Total person-days
- The sum of every team member's person-days.
A person's items are matched to their capacity row by their display name in Azure DevOps — the one identity both records share.
What you can click through to
- The total person-days card opens every item in the sprint.
- Each team member's row opens that person's own items.
- "Unassigned" opens the items with no one assigned.
Per-member hours, team days off and a working-day pattern are all optional settings in Azure DevOps, and most teams never set any of them. This page tells you plainly which of its numbers are real settings and which are assumptions, rather than presenting an assumption as measured fact.
- No sprint selector — Sprint Capacity always shows the active sprint, or the most recently finished one if none is active. You can't look back at an older sprint's capacity from this page.
- There is currently no click-through link between Sprint Capacity and Next Sprint Planning, even though the two pages are natural companions.