People Capacity in Release / Sprint / Team Iteration
Sometimes it is handy to know a person’s allocation so you can control the workload and see how much work is assigned, and whether you should add or remove or tasks. The People Capacity Board view shows project members and work items assigned to them.
The view calculates capacity just for single Iteration (Sprint), Team Iteration or Release. Capacity Calculation feature is useful alternative as it helps to plan across multiple work scopes displayed altogether.
The People Capacity Board view calculates each user's total effort to-do vs. available allocated work hours.
Supported Use Cases
People capacity feature works only when you plan Iteration (Sprint), Team Iteration or Release. Calculations are based on the facts of assignment of your work items to high-level planning work scopes. Start and End dates of high-level planning work scopes are considered in calculations.
The calculations do not take into account planned start and end dates assigned to work items directly. This capability is not implemented yet.
Personal capacity limits are shown only when the Effort of work items is estimated with the Ideal Hours unit. Points are not supported.
How to configure People Capacity view
Create a board view showing work items as cards, select Person as a lane and point the tool to the single scope of work specifying a filter for cards. When the filter is set in board view setup, People Capacity calculation starts to work on it.
The following Advanced Filters for cards activate People Capacity calculation in board view:
|People capacity for current Iteration|
|People capacity for other single Iteration|
|People capacity for current Release|
|People capacity for other single Release|
|People capacity for current TeamIteration|
|People capacity for other single TeamIteration|
Assigned effort calculation works when there are more than just one current Iterations / Releases / TeamIterations displayed. In the meantime, People capacity is calculated only for single Iteration / Release / TeamIteration so far.
Allocation information is shown for each person when a person row is expanded.
Assigned effort per user is calculated both for abstract points and ideal hours effort units. When effort unit selected in process settings is points, then points for stories and hours for tasks per user are added up separately. People capacity limit based on personal allocations and availability works only with hours effort unit selected in process settings.
How is the personal capacity limit calculated?
Personal capacity limit on People Capacity views is calculated from the number of remaining working days of the Sprint (Iteration) or a Release, number of Weekly Hours available for a Person and Percent Participating taken from user allocations.
Find more information in the advanced guide: How is the personal capacity limit calculated?
How is the sum of assigned effort for each Person calculated?
Assigned Effort totals are calculated as sum of EffortToDo values of RoleEfforts collection. As soon as a progress of a work item increases, its assigned effort decreases. Assigned Effort of Done items is always 0. More information: How is Progress calculated for work items?
The value sums up the Effort ToDo values of the Roles under which the person is assigned to the User Stories. Say, hours of Developer effort only when the person is assigned as Developer and hours of QA effort when the person is assigned as a QA Engineer.
For example, a task is estimated as 5h for Developer role and 0h for QA Engineer role. You assign John White as QA Engineer to this task. Then in the People Capacity view the card of the task will be shown in the row of John White's assignments. However total assigned effort for John White in the row header will be still 0h.