Team planning buckets

Within the Team Backlog module, you can use planning buckets to assign tasks to the different members of the team.

The team planning buckets are found on the Team pane to the right of the Team Backlog.

The buckets can display information for all sprints or a selected sprint in the release. Each bucket represents one member of your team.

For each team member you can see the following data:

  • The total number of items (stories) assigned to the team member.

  • How many of these stories are in progress and how many are done.

  • The amount of done (green) and remaining (blue) tasks assigned to the team member, compared to his or her capacity, in hours.

    Overplanned work is represented by in an inner red circle.

Tip: Click the team member name in a bucket to show only that user's items in the grid. To clear the filter and show all items again, click Show filter pane and click the X on the Owner field in the filter.

Drag stories from stories tab into buckets to assign them to a team members. Make sure not to exceed a member's capacity.

Caution: Assigning a story to a team member does not assign its tasks. Use the Tasks tab to make sure all tasks are assigned correctly.

You may want to filter the grid to show only tasks assigned to members of your team or unassigned tasks.

A team member's capacity is measured in hours. As you assign stories, the bucket displays the number of estimated hours in the stories' tasks that are assigned to this user in the selected sprint and team. Use the bucket widgets to avoid exceeding a team member's capacity.

Team member capacity: ALM Octane assumes each team member works 6 hours per day (you can see this in a team's Members tab). A team member's sprint capacity is the daily capacity times the number of working days in a sprint.

You can see a sprint's number of working days in a release's Timeline tab, in the Release Expected Capacity table.

If the bucket display does not display the expected results, check:

  • Story is assigned to correct user (owner)

  • Story points defined for the story

  • Tasks are created in the story

  • Tasks are assigned to correct user (owner)

  • Tasks have Estimated hours defined