# Team

![Teams can contribute to multiple programs (release trains) at the same time.](https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FF4FevljiRFZb3yAB7G0M%2Fteam-contribute-to-programs.png?alt=media\&token=0a106720-cdac-477f-a3bd-be0f4be13cdd)

Only *Ativo Programs for Jira* **administrators** can create, edit and delete teams ([more info](https://docs.ativo.io/configuration/permissions)).

Ativo Agile Programs for Jira uses its own team configuration. Jira cloud also has team definitions, but these do not contain the necessary scope information. Sorry 🧡.

You can align with the "Advanced Roadmaps / Plan" team definitions (included in Jira Premium and Data Center) by referring to the the Jira boards or JQLs in Ativo. 

### Create a new team (based on a Jira board)

To create a new team, using a Jira board:

* Open Ativo Programs 
* Click on ***Settings*** and then on **Teams**
* Click on the **Create Team** button
* Select the dedicated **Jira board** that the team is using. Ativo will use the Jira filter of the board as the scope for the team, as well as the board mode and estimation settings.
* Click **Create**

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FCIKHdeBjZhAu2qhxjIC7%2Fimage.png?alt=media&#x26;token=d8261507-e45a-41fa-9652-e8b869c3ee6a" alt=""><figcaption></figcaption></figure>

### Supported Jira boards

A Jira board is supported if it:

* Has a [JQL filter that is supported in Ativo](https://docs.ativo.io/configuration/project-and-jira-jql-filters)
* Is a Scrum or Kanban board
* Has an estimation that is either Story Points, Man Days or Issue Count. When using Story Points, all Ativo teams should use the same Jira field. A Jira admin can select the Story Points field to use in Jira via (Jira settings > Apps > Ativo Programs > Fields ). If not selected, the default Jira Story Points field is assumed.\ <br>

  <figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FxzE55XvFENCUvjdqUjfi%2Fimage.png?alt=media&#x26;token=be4972bc-9dd8-450a-aaee-873bedea9c95" alt=""><figcaption><p>Jira admins can set the Story Points field to use in Ativo.</p></figcaption></figure>

### Create a custom team

Create a 'custom team' if the team is not using a dedicated Jira board (e.g. no board exists, or it is shared with multiple teams).&#x20;

To create a custom team, do the same steps as above when creating a team using a Jira board. When the modal is open, select ''

* Open Ativo Programs&#x20;
* Click on ***Settings*** and then on **Teams**
* Click on the ***Create Team*** button
* Fill in the configuration information (see below)
* Click **Create**
* Click **Submit** (on the main team overview page)

Configure a new team:

* **Team name** - used as a label, e.g. on the program board.
* **Team key** - used when importing / exporting data. Choose something meaningful.
* **Mode** - set to *Scrum* or *Kanban.* With *scrum*, a team will plan stories in sprints. With *Kanban*, the *due date field* is used instead to map stories to sprints at program level.
* **Estimation** - set to *Story Points*, *Man Days* or *No estimations*, depending on how the team estimates work. Each team can use its own estimation method. Totals at feature and program level will be consolidated with a standard conversion rate of 1 MD = 1SP for teams using man days, and 1 ticket = 1 SP for teams not using estimations.
* **Jira filter (scope)** - let Ativo know which Jira issues the team is working on. the scope can be defined as a Jira projects (in case each team has a separate project), or a more complex filter in case teams are working on multiple projects, or are sharing Jira projects.&#x20;

{% hint style="info" %}
If you haven't decided on how to structure team scopes yet in Jira, we suggest to use a “one Jira project per team” configuration. This allows you to create flexible and agile workflows for each team.&#x20;
{% endhint %}

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2F1Q1TB2W3gx1kpkoQMSkC%2Fcreate%20team.PNG?alt=media&#x26;token=22b62a55-0370-4b2d-9cce-fe4e5e8162f4" alt="" width="563"><figcaption><p>Team creation form</p></figcaption></figure>

### Switch between "Jira board" and "custom" team configurations

You can switch a team configuration from 'Jira board' to 'custom' and vice-versa. To update an existing team, click on the 'more' and then 'edit' button of the team. Then click on 'Configure team in a custom way' or 'Configure team using a Jira board'.

How to tell the difference between both configurations? Teams configured using a 'Jira board' have a 'Jira board' selection. Teams configured in a custom way do not refer to a 'Jira board'.

When possible, use a 'Jira board' configuration, as it allows for a faster sprint selection in the Period configuration screen.

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FjD5RGDYR86YzZAe4iANW%2Fimage.png?alt=media&#x26;token=4bd07815-3627-426e-8d66-bb6f7739eb8d" alt=""><figcaption><p>Edit a team configuration</p></figcaption></figure>

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FMCAsDkdlu8Hnm9dcPajB%2Fimage.png?alt=media&#x26;token=c0f6d508-7ba5-44c1-bf77-f8b220356a00" alt="" width="563"><figcaption><p>Switch from 'Jira board' to 'custom' team configuration</p></figcaption></figure>

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2FvYIxoOUvEwMqtBLh1cec%2Fimage.png?alt=media&#x26;token=80042c95-52c5-451e-8137-cb3400caf320" alt="" width="563"><figcaption><p>Switch from 'custom 'to 'Jira board' team configuration</p></figcaption></figure>

### Archive a team

Archiving a team will remove the team from all programs and all periods.&#x20;

To archive a team:

* Click on the more options button and then on archive.
* Confirm you want to archive the team.
* Click on ***submit***

<figure><img src="https://2916206105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBAGNud2YIYXdGXre7dQK%2Fuploads%2F9JG7EhK404t11JtQDXAj%2Fimage.png?alt=media&#x26;token=8f6dd8bd-59e0-4fc2-814f-9e8c8ac704bc" alt=""><figcaption><p>Archive a team</p></figcaption></figure>

You can unarchive an archived team by clicking on the more options button and then selecting unarchive.<br>