Skip to main content
System StatusContact Support
VersionOne Community

Release Capacity Planning for Teams

This feature is available in Enterprise and Ultimate editions.



To view team capacity, the Teams feature must be enabled.

With the Teams feature enabled, Release Capacity Planning is an activity that teams use to determine bottlenecks early and only commit to work they can successfully complete. In Lifecycle, you can get a see these bottlenecks by viewing team capacity details on the Release Scheduling page.


As teams negotiate and detail out their workload during release planning, the system shows each team's current load in relation to it's capacity. For component teams planning work across multiple projects at once, the system ensures that an accurate picture is shown by factoring in work from other projects that will eat into the team's capacity as well.

Enabling Release Capacity Planning for Teams

Team capacity details don't automatically display by default; you must enable/configure them by setting the target velocity for each team. The Target Velocity field is located in the Team details view and allows teams to record their typical velocity using their own recent history as a guide.

  1. From the Admin menu, select Teams.

  2. Click the Edit button next to a team to open the details view or create a new team.

  3. Enter the project details as appropriate, enter the Target Velocity, and then click Save.

Note that after you enter the team's target velocity, the system automatically calculates the team's release capacity based on the duration of the release.

Viewing Release Capacity Details

On the Release Scheduling page, team details can be seen in two ways:

  • In the progress bars, which show a high-level graphical view of the team's target estimate.

  • Expand the Team Details section to see team-level allocations vs. team capacity.
    Note that the dark blue progress bar shows any work assigned to the team in other projects within the same timeframe. This highlights the need for multiple product owners to coordinate their relative priorities with respect to the team's workload.


Hovering over bars for an individual team will reveal the following metrics that can be used to ensure the team is not over committed for the selected release:



Closed Estimate

The total amount of completed Estimate for the selected Team in the selected Release and any sub-releases. This number includes Backlog Items that are Closed and those that are in a Status value assigned to the Complete status.

Other Project Estimate

Total remaining Estimate, assigned to the selected Team, in other Projects/Releases that have overlapping dates.  This number is calculated by determining the Estimate per day in the overlapping Project/Release and then multiplying that by the number of days the two Projects/Releases overlap.

Open Estimate

The total amount of remaining Estimate for the selected Team in the selected Release.

Target Estimate

The amount of Estimate the Team can deliver based on the Team's Target Velocity and the amount of time in the Release.  The number is calculated by multiplying the Team Target Velocity value by the number of Target Velocity periods in the Release. 

Days left in Project

The total number of days remaining in the Release.

When setting the team's target velocity, you can see the team's historical velocity to help guide what's realistic for them. We recommend that you review this information from time to time to make sure that the target set is realistic given the team's current velocity.