Share this page

# Teams

Build teams, assign users to them, and determine the capacity of each team.

In this topic:

## 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.

The default assumption is 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 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.

## Share teams between spaces

Workspace admins can define teams for an individual workspace. Teams cannot be shared across workspaces.

Space admins cannot define teams for isolated or shared spaces.

## Create a team

This section describes how to create teams.

To create a team:

1. Open the global menu and select Administration > General Settings.
2. Select a workspace.

3. Go to the Teams tab.

4. Click the Add Team button to add a team.

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

   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.

6. Click Add to complete the team creation.

   Tip: To immediately add members to the team, click Add & Edit and select the team's Members tab. For details, see Edit team members.

## Assign teams to releases and programs

Assign teams to releases.

You can also assign teams to programs. This helps you assign work items to teams according to their program association.

To assign a team to releases and programs:

1. Open the global menu and select Administration > General Settings.
2. Select a workspace.

3. Go to the Teams tab and click the team ID to open the team you want to edit.

4. Go to the Details tab and do the following.

   Step | Details
   --- | ---
   Assign a team to a release | In the Releases field, select one or more releases. To automatically assign this team to all releases that will be created from now on, select Assign to new releases.
   Assign a team to a program | Add the Programs field to the form. In the Programs field, select one or more programs.

5. Click Save.

## Edit team members

Add and remove members of the team, and manage team members' capacity.

To edit team members:

1. Open the global menu and select Administration > General Settings.
2. Select a workspace.

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

4. In the Details tab, set the team leader.

5. In the Members tab, click Assign members and select workspace users to add to the team.

6. Adjust members' default daily capacity (in hours) if necessary. Adjusting the default daily capacity will impact the team member's capacity in sprints to which the team member has not yet been assigned.

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

   Note: When you remove a member from the team:

   - The member is removed from the team but the user remains in the list of workspace users.

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

## Adjust a team's expected velocity per sprint

Adjust a team's expected velocity per sprint. This determines the team's capacity.

To adjust a team's expected velocity per sprint:

1. Open the global menu and select Administration > General Settings.
2. Select a workspace.

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

4. In the Velocity tab, adjust the team's expected velocity per sprint in each release.

   1. Select a release.
   2. Specify the sprints in which the team is available.
   3. For each sprint, enter an Expected velocity. This is the number of story points that you expect 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 see what the team actually achieves in each sprint.

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

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

## Edit team calendars

You can associate calendars with teams. Using calendars, you can create events during which team members are not available to work on their backlogs. Examples of events could be holidays, team fun days, or off-site project kickoffs. Calendar event durations are used for time-related calculations.

For details, see Workdays and calendars.

## See also

- Releases
- Plan a release
- Team backlog

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.3 All View Local Help Center View Online Help Center Version: