Planning Capacity: Calculation of Team Iteration load

Edit online

We've recently introduced a new Planning capacity for future Team Iterations Solution. Let's go into more detail and see how it may work for you and your team.

The solution is helpful for the following scenarios:

Planning capacity for Teams without Allocations 
Planning Capacity for Teams with Project Allocations

See, the topic Planning Capacity: Calculation of Team Iteration load for more information.

Basic Scenario: Planning Capacity for Teams without Allocations

Role: Scrum Master.

Details: Your team estimates each work item, you know the average or planned Capacity limits for upcoming Team Iterations. You do not use Allocations, all work is either from 1 Project or there are no restrictions on how the work should be allocated between several Projects. You want to plan your team capacity effectively (see if the team is underloaded or overloaded) inside Targetprocess without any other tools.

Preparations

First of all, you should add a board with this setup: Team Iterations and Teams as lanes, Features and User Stories as cards.
Then, go to the Team Iteration(s) details page and add the value of planned capacity into the "Capacity" field.

Results

As a result, you will see the Team Iteration load badge in each Team Iteration / Team cell, that indicates the current load of the Team Iteration. The system compares total assigned effort of work items to Team Iteration capacity.

Moreover, the color of the badge will show whether the Team Iteration is overloaded or not.

On click you will see details: the subtotals for each Project, selected in view setup. From the details pop-over you can navigate to the Team Iteration's entity details view by clicking on its badge.

Advanced Scenario: Planning Capacity for Teams with Project Allocations

Role: Scrum Master.

Details: Your team estimates each work item, you know the average or planned Capacity limits for upcoming Team Iterations. Your team uses Allocations, it is important for you that the percentage of Project Allocation is kept. Let's say, you plan 30% of work from Project A and 70% of Project B. Your goal is to plan Team capacity effectively (see if the Team is underloaded or overloaded) inside Targetprocess without any other tools. You want to be sure that you follow the Allocation percentage while planning Capacity.

Preparations

Let's start by adding a board with the following setup: Team Iterations and Teams as lanes, Features and User Stories as cards
After that, go to Team Iteration page and add values of planned capacity into "Capacity" field
And finally, set to Projects

Results

The Team Iteration load badge is shown for each Team Iteration / Team cell and indicates the current load of Team Iteration. The system compares assigned effort of work items to total Team Iteration capacity and assigned effort for each Project to Project Capacity.

Let's have a look at one example:

There is the team "Alaska" with Capacity 320h for a Team Iteration.

Team has 30% and 70% allocations to projects "Android App" and "iOS App". It means that the proportion of total assigned effort should keep this percentage.

So the capacities for Projects are:

"Android App": 320*0,3 = 96h

"iOS App": 320*0,7 = 224h

We highlight the capacity badge in red even if the total capacity is not overloaded, but the allocation percentage is not kept. The capacity details will explain which Project is overloaded.