Contents: |
---|
The Resources panel provides a convenient way to track the assigned workload.
Enabling the Resource panel allows you to easily see each resource's (assignee’s) workload, measured in hours and color-coded based on capacity.
Workload data is specific to filters, meaning only tasks within the current view are considered in the workload calculation. Utilize Quick Filters or the Search Box to tailor tasks and explore various scenarios.
Typically, effort is evenly spread across a task, but you can adjust the distribution within the Resources module. For further details, refer to Workload contouring.
Workload details dialog
Thanks to the workload details dialog, you can better understand what data is presented in the panel.
Click on a colored tile to open the pop-up:
Workload vs Capacity Thresholds
The same rules apply to the Resources panel in the Gantt module and the Resources module itself.
Capacity = 0
Capacity is equal to 0 when a resource is unavailable on a given day (because of Workload Plans, Holiday Plans, or individual Absences). The related user’s capacity is automatically set to 0 when the user is archived. Capacity can equal 0 for an individual or a Team. In that situation, in the Resource grid (resources module) and the Resource Panel (Gantt module), the App uses the following algorithm (applies only for tasks that have automatic contouring mode): the task effort is distributed between non-working days of the resource if all days from the task's period are non-working days (sum of capacity from that period is 0), The task effort is not distributed between non-working days of the resource if only a part of the task's period consists of non-working days (the sum of capacity from that period is >0). As a result, if the capacity (of a resource or a team) is 0 and there are some tasks with effort estimation in that period: in the Resource grid, the Workload cell is red, and it displays the Workload distributed according to the above algorithm. In the Resource Panel, the Workload cell is visible, red, and displays Workload distributed according to the above algorithm.
In that case, task effort is distributed only between working days.
The example below shows that a resource is overloaded, but you can't see why. To find out the workload details, go to the Resources module and check the workload of the assigned tasks.
In the example below:
Resource (Christopher) is absent for a whole week (11th to 15th of October)
For a task that falls only on the days he is absent, capacity has been evenly distributed
For a task that falls partially on his workdays and partially on the absent days, the workload is distributed only on the days he works (has a capacity).
When the total availability of a Resource exceeds 100%, a warning will be displayed.
Effort Modes
The general rule is that effort is evenly distributed over the duration period. You can switch between three effort modes:
Original Estimate
Use this mode during the planning phase as the Original Estimate of time tracking is used and it is assumed that assignees did not start logging work at this point.
In this mode, the Original Estimate of Time tracking is evenly distributed over the duration period. For example:
Remaining Estimate
Use this mode to monitor the project's execution. In this case, the Remaining Estimate of time tracking is used. The remaining effort is evenly distributed starting from the current date.
In this mode, the Remaining duration is evenly distributed over the remaining task duration, starting from the current date, and the Spent time is evenly distributed over the past duration. In the example below, there is no logged work; hence, there is no indication of effort before the current date marker.
Story Points
This mode monitors the project’s execution in Story Points. To use this mode, ensure the story points value has been specified for tasks.
Aggregations
Display the workload as aggregated values in the following intervals:
Daily
Weekly (weeks count starting from Monday through Sunday)
Monthly