Manage teams

Workspace admin permissions are required.

Create teams in each workspace, and assign the teams to the releases on which they will work.

Tip: Are you going to manage ALM Octane users using LDAP? If so, we recommend that you export LDAP users into ALM Octane before continuing. For details, see Set up LDAP authentication.

 

Overview

Create teams in each workspace, and assign the teams to the releases on which they will work. Then estimate a velocity at which the team is expected to work, in story points. This determines the capacity of your release—how much functionality you can deliver according to the release timeline and the teams working on it.

ALM Octane assumes that each team member works 6 hours each day. This determines the capacity of your team—how many tasks your team can handle in a sprint.

Once teams are created, you can assign backlog items in ALM Octane to specific teams. This indicates who is responsible for the different items.

You define a workspace team's settings, and users can track the team's performance across releases.

Create teams

  1. In Settings , click Workspaces and select the workspace where you want to create a team.

  2. In the Teams tab, click + to add a team.

  3. Enter values for the team, such as name and estimated velocity, and select a team leader for this team.

    Tip: The expected velocity is the number of story points that you expect the team to deliver in each sprint, based on the team performance over time.

  4. Click Add to complete the team creation.

Assign a team to releases

  1. In Settings , click Workspaces and select the workspace where you want to assign the team.

  2. In the Teams tab, click the team ID link to open the team you want to edit.

  3. In the Details tab, in the Releases field, click the down arrow and select one or more releases.

  4. To automatically assign this team to all releases that will be created from now on, do one of the following:

    • In the details page: Select Assign to new releases

    • In the grid: Select Yes in the Assign to new releases column.

Edit a team's details

You can edit team member details in one of the following ways:

In the Workspace Settings
  1. Select the workspace where you want to edit the team.

  2. In the Teams tab, click the team ID link to open the team you want to edit.

  3. In the Details tab, set the Team lead.

  4. In the Members tab, select members from the list of ALM Octane users and add them to the team.

  5. To remove a member from the team, hover over the list of team members and click the X next to the relevant name.

    Tip: When you remove a member from the team:

    • The member is removed from the team but the user remains in the list of ALM Octane users.

    • Any backlog items assigned to this team member remain assigned.

In the Team Backlog module
  1. In the Team buckets area, with a release and sprint selected in the filter, click the Edit button above the buckets:

  2. In the Team Management dialog, select the Members tab.

  3. In the Members tab, click Assign members select members from the list of ALM Octane users and add them to the team.

Adjust a team's capacity per sprint

  1. In Settings , click Workspaces and select the workspace where you want to set the capacity.

  2. In the Teams tab, click the team ID link to open the team you want to edit.

    Tip: If the relevant field's column is not displayed in the grid, click and add the column to the grid.

  3. In the Velocity tab, fine-tune the team's expected capacity per sprint in each release.

    • Select a release.

    • Specify the sprints in which the team is available.

    • For each sprint, enter an Expected velocity. This is the number of story points that the you except the team deliver in each sprint.

      Tip: The Velocity grid also displays an Actual Velocity column that reports the actual velocity achieved in a sprint so you can get a realistic view of what the team is achieving for each sprint.

    The updated capacity information is reflected in the Backlog and Team Backlog modules.

Note: For any given sprint, the expected capacity may not be the same as the expected velocity entered in the Details tab for the team.

Back to top

See also: