The Team Capacity feature in Kendis is a critical tool for accurately calculating and visualizing your team's available capacity for each iteration (sprint) within a Program Increment (PI). It offers the flexibility to define capacity either at a granular individual user level or a broader team level based on estimated velocity, ensuring realistic PI planning and commitment.
This capacity data is vital as the total capacity per sprint directly feeds into the team-specific areas of the main Program Board, enabling teams to plan their Feature commitments against their actual bandwidth.
Key Benefits of Team Capacity
Benefit | Description |
Accurate Planning | Calculate precise capacity per iteration using Story Points or Number of Stories, leading to more realistic Feature commitments. |
Execution Tracking | Provides real-time visibility into planned Capacity, committed Load, and delivered Done metrics, tracked both at the Team and Individual member level throughout the PI execution phase. |
Flexible Definition | Supports defining capacity at the Individual User Level (sum of team members' capacity) or at the Team Level (a single velocity value for the entire team). |
Direct Board Integration | The calculated total team capacity for each sprint is automatically reflected in the Team Area of the main Program Board, assisting the team with planning their stories and features. |
User Management | Easily add users from your integrated Agile tool (e.g., Jira), select existing Kendis users, or create non-Kendis users (who do not consume a Kendis license). |
Program Visibility | The top section provides a simple, aggregated overview of team capacities across the entire PI at the Program Level. |
Reporting & Analytics | Capacity data is used in analytics views like Delivery by Teams and Progress by Team to track performance against commitment. |
Detailed Navigation and Setup Guide
1. Accessing the Team Capacity View
Navigate to the Board: Ensure you are on the main Program Board for the relevant PI (e.g., "PI Q1 2025").
Open the More Menu: Click the "More" dropdown button, typically located near the top-right corner of the board (next to the "Board Settings" button).
Select Team Capacity: In the dropdown menu under the Tracking section, click the "Team Capacity" tile.
2. Program Level Capacity Overview
The Program Level Capacity table is located immediately below the main header settings.
This table lists every team in the PI or Program Board.
The cells under each Iteration show three key metrics for that team: Capacity, Load, and Done (e.g., 20 42 32).
The Total column provides a total capacity sum, load sum, and done sum for all iterations for that team.
This section gives you a simple, centralized overview of your team capacity status at the PI level.
3. General Settings and Configuration
Once in the Team Capacity view, you can adjust the primary capacity settings:
Default Per User Value (Top Left):
This setting is a Program-level default and applies to all users created on the board. It is located in the top-left corner of the screen, above the Program Level Capacity table.
The platform sets a Default per user capacity, typically 8 (representing 8 Story Points per user per sprint).
To change this value, simply click on the number field and enter a new default capacity value. This new value will be used as the starting capacity for all newly added users, but will not overwrite existing entries.
Capacity Unit Toggle (Top Right):
By default, capacity is calculated By Story Points. This toggle is located in the top-right area of the screen.
Click the dropdown next to the capacity unit to switch the calculation method to By Number of Stories.
View Settings (Top Right):
Click the "Settings" (⚙ icon) dropdown, located next to the Capacity Unit Toggle, to configure the visual columns for individual capacity.
Toggle the Show Location and Show Role switches to display or hide these columns in the capacity table.
The Export option allows you to download the capacity data.
Filter Teams (Top Right):
Click on "Selected Team X/Y" (e.g., "Selected Team 4/4"), located in the far top-right corner, to open a filter dialog.
Use the checkboxes to select or deselect specific teams to view.
4. Defining Capacity (Individual User Level)
This is the recommended method for granular planning, involving entering capacity for each person on the team. The sum of all individual capacities will be the team's total capacity for that sprint. This section is located under the Teams Capacity heading in the lower half of the screen.
Enable Editing: Under the Teams Capacity section, locate the target team (e.g., "Team Venus") and click the "Enable Editing" link on the far right of the team row.
Add New Users:
In the "New user:" field, click the dropdown. When a user is added, their initial capacity is automatically set based on the Default per user value (see Section 3).
You have three options for adding users:
Select Existing Kendis User: Choose a name from the list of existing platform users.
Search From JIRA: Search for and select a user from your connected Agile tool (e.g., Jira).
+ Create: Click '+ Create' to create a non-Kendis user. Provide a name and a temporary email address. These users are marked as non-Kendis users in the User Directory and will not consume a Kendis license.
Select the appropriate Role and City, State or Country Name (Location) from the dropdowns next to the user selection box.
Click the "Add" button. The user is now listed in the team table.
Set Individual Sprint Capacity:
For the newly added user, click into the input field under each Iteration column (e.g., "Iteration 1: 10 Nov - 22 Nov").
Enter the specific capacity value (Story Points or Stories) for that user for that iteration. You can overwrite the default value here if needed.
As you enter values, the Sum (total for the user) and the team's Total Capacity row at the bottom will automatically update.
Complete and Save: Once all users and their capacities are entered, click the "Done Editing" button at the right end of the team section.
5. Defining Capacity (Team Level)
If you prefer to use a flat velocity for the entire team rather than tracking individual user capacity, you can do so by creating a single team placeholder within the Teams Capacity section.
Prepare the Team Capacity Field: Navigate to the relevant team in the Teams Capacity section.
Create a Team Placeholder Users
Click "Enable Editing" for the team.
Click '+ Create' under the user dropdown.
Provide the team name (e.g., First Name: Team, Last Name: Alpha) and a placeholder email (e.g., team.alpha@kendis.io).
Set Team Velocity per Iteration:
For the single Team Placeholder user row, enter the team's calculated velocity/capacity value directly into the input field for each Iteration column (e.g., 40 for Sprint 1, 34 for Sprint 2, etc.).
This single user's capacity now represents the entire team's capacity.
Complete and Save: Click the "Done Editing" button.
6. Capacity Integration with the Program Board
The final, calculated total of the team's sprint capacity is automatically pulled into the Team Area on the main Program Board. This is where teams use the capacity information to assist with their planning.
Look at the team rows on the main Program Board. The iteration columns will display the committed load against the total available capacity (e.g., 37 / 65), where 65 is the capacity value set in this Team Capacity screen.
This immediate visual feedback helps the team decide how many stories or features they can realistically pull into each sprint during PI planning.
7. Tracking Capacity Utilization and Execution
During the execution phase of the PI, the capacity planning view automatically transforms into a powerful tracking tool, showing the utilization of the planned capacity for each iteration, both at the team and individual level.
Team Level Tracking (Program Level Capacity Table)
In the Program Level Capacity table (Section 2), each iteration cell displays three metrics (e.g., 20 42 32):
Capacity (20): The planned capacity for the team for that sprint (the value you set in the Teams Capacity section).
Load (42): The total Story Points of all stories assigned to the team for that specific sprint/iteration. This represents the team's committed load.
Done (32): The total Story Points of all stories completed (marked as 'Done' in the source Agile tool) by the team for that specific sprint/iteration. This represents the delivered value.
This view provides an essential summary of how the team is performing against its planned capacity and committed load, sprint by sprint.
Individual Level Tracking
While the individual rows in the Teams Capacity section focus on planning, their assigned stories directly contribute to the Team's Load and Done metrics:
Individual Load: When a Story is assigned to a team member in the underlying Agile tool (e.g., Jira) and placed on the Kendis board, the story's points are added to that team member's total load for that sprint.
Individual Progress: As that team member completes the story, the points move from Load to Done, updating the overall team metrics instantly.
The system uses the individual assignment of stories to accurately sum the Load and Done metrics, providing granular visibility into performance down to the team member level during execution.