Skip to main content

Capacity tab in Context

What the Capacity tab shows, how each figure is calculated, and where the hours are set.

The Capacity tab of Context compares what your people can take on in a period with the work they committed to, the work they still have open and what they will finish next — for the view, for each team and for each person. Every figure shows how much it changed against the previous period, so you can tell whether things are getting better or worse.


​

The cards


​

  • Load — the committed work over the capacity. Around 100 % the plan fits; well over it, it does not. Its pill says it in words: Underloaded (under 70 %), Room to spare (70–84 %), Balanced (85–105 %), Just over capacity (106–110 %) or Over capacity (over 110 %).

  • Capacity — what the people can deliver in the period. In hours, the hours they can work without absences; in points or tasks, those hours at the pace they usually finish work. The card shows how it is calculated; hover each term to see what it is.

  • Committed — the work they took on in the period: done in it, in one of its sprints, or in progress and moved in it.

  • Workload — the work assigned to them that is not done yet, how many weeks it takes them and when it is done: the working days at the pace they really deliver, and the date. It also lists the open work without an owner and the work nobody has moved in 90 days.

  • Next period — what they should finish in the next sprint (or the next two weeks, without sprints), with its formula and range.

  • Finished per period — what they finished in each of the last three periods, and the forecast for the next one. Each bar counts everything finished in its dates, in the sprint or not, leaving out days of work closed in bulk: it is the pace, not the done work of Committed.

  • By team, Load by person and Workload by person — the same figures for each team and each person. The ⓘ of each column says how it is calculated, and the detail of a number (the available hours, the people of a team, the weeks of work) shows when you hover it. The filter of the first column finds a team or a person.


​

How it is calculated


​

  • The unit: hours when half the work items carry an hour estimate (on themselves or on their sub-tasks), points when half carry story points, tasks otherwise. Whoever edits the view can fix it from any card's ⋮ › Change unit. In points and tasks, sub-tasks are not counted, as in your tool's sprint reports.

  • Available hours: each person's working day on weekdays, minus their absences and, when the unit is hours, the meetings ahead they accepted with other people invited. The working day is the first of these that exists: the person's individual hours, the hours your work tool keeps for them (for example, the capacity of an Azure DevOps sprint), their position's week, your organization's week, or 8 hours.

  • Pace: what they finished per available hour over the last three closed sprints of their boards, or the last three periods of two weeks when there are no sprints. Each team and each person goes at their own pace once they finished at least three work items in those periods; otherwise, at the group's.

  • Days left out of the pace: a day far above their usual one — old work closed in bulk, an import — would make the pace look much faster than it is. Each day is compared with how much their usual days vary, and a day that stands far out is left out of the pace, the capacity and the forecast, with its hours. A busy day of real work stays. Finished per period says which day was left out. It still counts as committed work.

  • Capacity = available hours × pace (in hours, the available hours).

  • Load = committed ÷ capacity.

  • Completion = work items finished ÷ work items committed to. A story counts once for each person with tasks in it, and is finished for them when their tasks are.

  • Workload: assigned and not done, in a sprint still running or moved in the last 90 days. Weeks of work = workload ÷ what they can take on in a week (their hours in the next two weeks, at their pace); over two weeks it does not fit in them.

  • When the workload is done = workload ÷ what they finish in a working day at the group's pace, with the hours they have ahead, counted in working days from the end of the period.

  • Next period = what they finish per period on average × the hours of the next period ÷ their usual hours per period. The range goes from their slowest to their fastest period; absences already loaded for the next period count.

  • Change against the previous period: the same figure over the period of the same length just before, measured at the same pace. Capacity going up is green; the load is green when it gets nearer 85–105 % and red when it moves away; committed work and workload are blue. Next period is compared with the last period they finished.


​

Where the hours are set


​

Everything about hours lives in Settings → Working hours:


​

  • Organization — the organization's week.

  • Positions — the week of each position, given to everybody who holds it.

  • People — a person's individual hours, which win over their position's.

  • Absences — a team at a time: add an absence for a person or the whole team, or ignore one that comes from a tool or a calendar.


​

Show details and filters


​

  • Every Show … link and every number in blue opens the rows behind it, with a filter on each column and Export to CSV: the committed work of a team or a person, their workload, what is in progress, their next two weeks day by day (with each day's meetings, in hours), the work nobody moved in 90 days and what they finished.

  • Filtering the committed work, the workload, the work without an owner or the finished work from its Show details measures that figure with the filter for everyone who opens the view; Remove filter goes back.

  • On any card, ⋮ › Duplicate makes copies measured over the work item types you tick.


​

Related articles


​


​

Did this answer your question?