Manage the team backlog

After setting up the overall release plan, you can assign each user story to a team and user to start carrying out your development plan.

You can do this from the Team Backlog module, or if not available, the Backlog module.

The Team Backlog module is part of the Agile Manager offering within ALM Octane.

Select an image to navigate directly to the topic about this phase and learn more.

Prerequisites

  1. Make sure your workspace admin set up the release timeline and teams.

    • The team must be assigned to a release and sprint.

    • The team must have members assigned.

    • Team capacity (in story points) must be defined.

  2. In the Team Backlog module, select a release, sprint, and team to view the relevant data.

    If you are using the Backlog module, filter your data by release, sprint, and team.

  3. Make sure backlog items have been assigned to your team, in the selected sprint.

  4. Open the Stories tab and reevaluate the estimated effort assigned to each story, in story points. Release, sprint, and team progress are tracked in story points.

Back to top

Edit your team's capacity per sprint

Leader permissions are required.

If your team has variable work rates during a specific release or sprint, you can edit the expected capacity for these periods instead of using the default velocity capacity specified in the Teams tab of the Settings area.

For details, see Set sprint velocities.

Back to top

Break stories into tasks

  1. Break your stories into tasks that describe the smaller steps that make up the story. Do one of the following: 

    • In the Stories tab, right click a story and select Add Task.

    • Open a specific story, select the Tasks tab, and click +.

    • In the Team Backlog, make sure at least one story is displayed, and open the Tasks tab. Select the Board view , expand a story's row, and click + inside the board cell.

  2. Assign a task in one of the following ways:

    • Click the ID link for the task, and in the Details task of the tab, set the Owner.

    • Drag a task card to a team member bucket.

  3. In the Details tab of the task, estimate the effort needed for each task, in hours.

You can now plan and track each team member's work in hours.

Team members can only delete items that they have created.

For details on using the task board, see Work on your stories.

Back to top

Assign stories using team member buckets

In the Team Backlog, open the Team pane on the right to see the team member buckets.

From the Stories tab (either in the Smart List view or the Grid View), Tasks tab, or the Board View in the Stories tab, drag the stories into the team member buckets.

The team member bucket is then updated with the story details:

Caution: Assigning stories to a team member does not assign its tasks.

Back to top

Track team progress

As a sprint progresses, you can track the team and individual progress:

Graph or chart Where? Description
Backlog dashboard widgets Backlog module

In the Overview tab, you can display the progress in the available widgets, including:

  • Story points by metaphase

  • Story points per feature type

  • User stories per team

Release planning buckets Backlog module

In the Planning tab, the Release planning buckets display progress of each team on the stories assigned to a sprint. The graph reports the total number of story points in each phase:

For details on the release planning buckets, see Backlog planning buckets.

Team sprint progress graph Team Backlog module

In the upper left corner of the Team Backlog module (the sprint summary area), you can view a graph that displays the overall development status in the selected sprint. This graph displays the number of story points. In addition, it also shows the number of critical defects assigned to the team:

The progress is measured by story points assigned to all members of the team in the current sprint cycle.

Team member buckets Team Backlog module

Each team member bucket displays the progress on the stories and tasks assigned to the team members, as well as on defects assigned during the current sprint cycle:

Back to top

Next steps: