Release Capacity: Calculation of Team Load in Releases
- Agile Release and Iteration Planning
- Split Entities
- Generate Team Iterations for Release
- Calculate Capacity of Team Iteration automatically based on previous Velocities
- Planning Capacity: Calculation of Team Iteration load
- Planning Features into Releases: Effort Calculation
- Finish Action for Iterations and Team Iterations
- Backlog Planning and Management
If you are planning Release capacity for each team that is going to participate in a Release, the following solution may be helpful for you.
Role: Scrum Master, Release Train Engineer, Team Lead
Details: Several teams are working in the same scope of a Release time-box. Each team uses Team Iterations as smaller time-boxes in Releases. You know the average or planned Capacity limits for upcoming Team Iterations. Teams estimate each work item.
Step by Step Guide:
- Identify, which teams plan to participate in upcoming Releases by creating Team Iterations for them (these can be made automatically). All Team Iterations that are assigned to a Release will influence the total Release capacity of the team.
- Set Team's capacity limits in each Team Iteration.
- Add Metric to Release Custom field "Capacity"
Settings → Metrics → Add → Custom Formula
This metric will set the the sum of all Team Iterations capacities to the Release Capacity custom field.
- Add a board with Releases / Teams as lanes and Features and/or User Stories and/or Bugs as cards.
How is the capacity of each Team calculated for their Releases?
Total Team capacity for the upcoming Release is equal to the sum of Team Iterations capacities, that are assigned to the Release.
Imagine we have 2 teams: Team London and Team Berlin that are working on the scope of one Release. Each of the team has 3 Team Iterations. The planned capacities for these Team Iterations are known:
Team London Team Iteration 1 - 100 h;
Team London Team Iteration 2 - 100 h;
Team London Team Iteration 3 - 120 h;
Team Berlin Team Iteration 1 - 90 h;
Team Berlin Team Iteration 2 - 100 h;
Team Berlin Team Iteration 3 - 95 h;
How is the Release load of each Team calculated?
While planning each Team's work into Releases we calculate the sum of “Effort To Do” assigned to a Release and to the Team.
Note: if a Feature is in progress (say, it is 50% completed), only its remaining work (Effort To Do) will influence the Release load, not Total Effort.
Still have a question?
We're here to help! Just contact our friendly support team