---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Complete the prerequisites for converting teams to Agile Development 2.0 groups

# Complete the prerequisites for converting teams to Agile Development 2.0
groups {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Perform prerequisite steps to later ensure that the conversion of teams to Agile Development 2.0 groups is successful.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Importante:  
Agile Development 1.0 and its features such as Sprint burndown chart and release burndown chart are deprecated and no longer available. [Agile Development 2.0](https://servicenow-prod.fluidtopics.net/gga0oNl9eV22W~iuuhorLA "ServiceNow Agile Development 2.0 provides an agile software development environment for product-based or project-based efforts, using the Scrum framework. Implement a pure agile approach over the entire life cycle of a product, or a hybrid approach using agile methods within a traditional project structure.") provides the latest experience for supporting your Agile work methodology.

The team being selected should have at least one sprint that is current. The current
sprint should have a few completed and a few WIP stories. This is to verify that the
sprint burndown is updated correctly post conversion. If you do not have such a
team, you may select any team for conversion.

## Procedimento

1. Find out the sprints assigned to the team across all a release.  
   Nota:  
   Use this step to verify whether the assignment group is updated successfully across all the sprints.
   1. In the search panel in navigator, type rm_sprint.list to view the list of all sprints.
   2. Display the Team and Assignment group fields if not displayed.
   3. Apply the team name filter. The Assignment group field is empty.
   4. Capture the screen or export the list of all sprints. In the sample example, sprint 5 is the current sprint for the team being converted.

   {#steps-prior-conversion__ol_kxq_gsq_3gb}

2. Find out the stories that are associated with the sprints of the team being converted.  
   Nota:  
   Use this step to verify that the assignment group is updated successfully across all stories.
   1. In search panel in navigator, type rm_story.list to view the list of all stories.
   2. Filter out the stories belonging to the sprints noted in the preceding step.
   3. Display Sprint.Team and Assignment group fields in the list layout. The Assignment group field is empty.
   4. Capture the screen or export this list.
   5. Filter the story table to fetch the list of all stories belonging to sprints of the team being converted. Apply the following filter:sprint.release_teamSTARTSWITH\<name of the team\>

   {#steps-prior-conversion__ol_h44_swn_jgb}