Verify the conversion of Agile Development 1.0 teams to Agile Development 2.0 groups

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 1 Minute Lesedauer

    • Perform verification steps to ensure that the conversion of a team to an assignment group is successful.

    Vorbereitungen

    Role required: admin

    Warum und wann dieser Vorgang ausgeführt wird

    Wichtig:
    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 provides the latest experience for supporting your Agile work methodology.

    Prozedur

    1. Navigate to All > Agile Development > Groups.
    2. Verify that the team has been converted to an assignment group.

      If group appears here, it implies that the group type is already set to Agile Team.

      Group type is set to Agile Team in the screen shot

    3. Verify that the assignment group is updated across all the sprints of the team.
      It is the same sprint list that you have noted prior to conversion. This list must have the assignment group updated after conversion.

      Verify that the assignment group is updated across all the sprints of the team.

    4. Verify that the stories associated with the sprints of team have been updated with the assignment group.

      Following is the list of stories that were noted prior to converting to group:

      List of stories that were noted prior to converting to group

    5. Review the sprint burndown for the sprint that was noted prior to conversion.
      It must be same as it was prior to conversion.
      1. Open the rm_srpint table (rm_sprint.list), or open the assignment group.
      2. Click the current sprint.
      3. Mark any WIP story as complete.
      4. Review the sprint burndown that is to be updated with the completed story.

      Review the sprint burndown for the same sprint that was noted prior to conversion Burndown chart prior to conversion Burndown chart progress displaying the story completed after conversion

    6. Once the story is complete, the release burndown must also be updated correctly.

      For example, in the following screenshot, the burndown is updated correctly for the current release.

      Burndown is updated correctly for the current release How to navigate to a release Release burndown chart after conversion when one of the stories is completed

    7. For Group Velocity:
      1. Navigate to Agile Development > Groups.
      2. Review the velocity of the group. It must be same as it did prior to conversion.
      3. Complete the current sprint. It must display the velocity of group for the completed sprint in addition to the sprints that were completed before conversion.

      How to navigate to groups

      Use the Group velocity related link View the group velocity chart
    8. Once you verify the steps for one group, it is confirmed that the migration has completed successfully.
      You can repeat this procedure for all other teams one by one. This is a synchronous process, hence, you should perform these steps on one team at a time.