Estimated Effort and Capacity

Prev Next

Unplan Elements

Remove the items that have already been scheduled first.

  1. Open the release.

  2. Move items from the sprint to the release.

  3. Open the backlog.

  4. Move the items from the release to the backlog.

You can move multiple items at the same time. Hold CTRL to select them, and then move them together.

Estimating the elements

Stories and bugs should be estimated for:

  • Facilitate planning based on a team's capacity

  • Have metrics on the progress but also on the capacity of a team in the long term

These values can be set in the story and bug creation forms.

In this model, you need to add a value in the "Initial effort" field. Note that this field may have a name given by the project administrator.

Values are expressed in points.

For optimal use of the Backlog tool, you can also enter the "remaining effort".

It is located just below the "initial effort" field that was used to capture the item estimate.

User story for stopping the engine with progress tracking and acceptance criteria.

Capture Capacity

You can specify the team's capacity in points or days. In this model, it is expressed in points.

There are two methods:

  • Enter the capacity directly in the release
    Details of the first release including dates, total capacity, and status information.

  • Enter the capacity in each sub-milestone. This is the recommended method.
    The "Total capacity" field will automatically display the sum of the sub-milestone capacities.

Plan for capacity

The estimated effort of the milestone updates when you add an item to a release.

The sum of the effort of the items added to your milestone will be compared to the production capacity related to the milestone itself. If the initial effort is greater than the capacity, a colored reminder will highlight the excess.

Milestones overview showing capacity and initial effort for project planning tasks.