After creating a release plan, work with your team's items. Do this from the Team Backlog module or the Backlog module.
If your team has variable work rates, edit the expected capacity for these periods instead of using the default velocity capacity.
For details, see Set sprint velocities.
After setting up your release plan, assign each user story to a team member. Do this on a team-by-team and sprint-by-sprint basis.
To assign items to team members:
In the Details tab of the item, set the item Owner.
From the Backlog Items tab, drag the item to a team member bucket in the Teams tab.
Team member buckets are updated with the story details:
For details on what the team member buckets display, see Team planning buckets.
Caution: Assigning stories to a team member does not assign its tasks.
As a sprint progresses, track the team and individual progress.
To track team progress:
|Backlog dashboard widgets||Backlog module||
In the Overview tab, use available widgets, including:
|Release planning buckets||Backlog module||
In the Planning tab, the Release planning buckets display progress of each team. 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, view a graph that displays the development status for the selected sprint. This graph displays the number of story points. It also shows the number of critical defects assigned to the team:
You measure the progress 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 of the items, tasks, and defect assigned to a team member:
|Team commits widget||Team Backlog module||
The commits widget shows you the work your team has committed during the current time frame. ALM Octane breaks down the commits by story type:
Hover over the widget title for a reminder of the commit message format used to associate commits with each type of story.
See more information about changes committed by your team in the Commits column. For details, see Use the Commits tab to track committed changes.