Accessing the Report
On the main menu, select:
Reports > Team Capacity (in the Project/Release section or in the Member/Team section), or
Release Planning > Release Scheduling > Team Capacity (from Reports drop-down menu)
Enter the report filter criteria in the appropriate fields.
Click the Go button.
- Aggregation Type
- This parameter determines if the report aggregates Estimate on Backlog Items owned by the Team or Swag on Portfolio Items owned by the Team
- Portfolio Item Type
- This filter allows you to narrow the Portfolio Items being shown to those of the selected type.
Understanding the Report
The Portfolio Items listed depend on the Portfolio Item Type filter selection.
- When the Portfolio Item Type filter is set to "All", then the Portfolio Items listed are the top-most Portfolio Items in the selected Project or Program. These are the same Portfolio Items visible on the Portfolio Kanban and the Portfolio Tree when no filtering is applied.
- When the Portfolio Item Type filter is set to a given Portfolio Item type, then the Portfolio Items listed are the top most Portfolio Items of the selected type in the selected Project or Program.
For each Portfolio Item the "Planned" column indicates the Total Estimate or Swag value depending on the Aggregation Type filter value.
The value displayed in the Portfolio Item - Team intersection cell is determined by the "Aggregation Type" filter.
- When aggregating on Total Estimate, the value in this cell is the sum of the Estimate on all Backlog Items assigned to the Portfolio Item owned by the Team.
- When aggregating on Total Swag, the value in this cell is the total Swag on all Portfolio Items related to the displayed Portfolio Item owned by the Team. Note: because the Portfolio Item structure is hierarchical, double counting will occur both parent and child Portfolio Items have the same target team and Swag value. 1
The Teams listed are those that own work in the selected Project or Program and match the "Aggregation Type" filter.
- When the "Aggregation Type" filter is set to "Total Estimate", the report considers Teams that own Backlog Items for the Portfolio Item.
- When the "Aggregation Type" filter is set to "Total Swag", the report considers Target Teams on Portfolio Items.
For this reason, you may see a Team when aggregating one way (Swag for example) that does not appear when aggregating on the other (Estimate for example).
Under each Team name the report shows the Team Capacity, the amount of work Planned for the Team and the difference between these two numbers.
- The Capacity row for each team is calculated based on the Target Estimate or Target Swag value, depending on the Aggregation Type selected, set for the Team and the duration of the Project. For example, if a Team can deliver 10 points per week and the project is 10 weeks long, the Capacity of the team is 100 points.
- The Planned row for each team is the sum of the values in each Portfolio Item row. This will be the Total Estimate or Total Swag owned by the Team, depending on the Aggregation Type selected.
- The Difference row for each team is calculated by subtracting Capacity from Planned. Positive numbers indicate the Team has remaining capacity, negative numbers indicate the Team has over planned based on the calculated Capacity.
The report includes a row for Backlog Items not assigned to a Portfolio Item when the "Aggregation Type" filter is set to "Total Estimate". This enables an understanding of how much work is being delivered by Teams that are not part of a Portfolio Item.
1. Ideally the Portfolio Items in a given release, or PI, are the lowest level Portfolio Items that have no child Portfolio Items (typically referred to as Features). In this scenario, there is no concern for double counting. However, there are occasions where an organization has a "Feature" assigned to a Release, or PI, that has child Portfolio Items to account for smaller parts of the features. These child Portfolio Items are often refered to as sub-features and they are frequently delivered by multiple Teams. In this scenario, when there is a need to understand how the sub-features impact the capacity of each Team, the sub-features also have a Swag value. Having Swag on a Feature and sub-features, in the same context (Release or PI), will result in double counting on this report. You can avoid this by only using Swag on the actual Portfolio Items being planned for the Release/PI and not at multiple levels.