Configuring Azure DevOps projects for SAFe

concept australia Updated Sep 10, 2026 1 min read configuring-azure-devops-projects-for-safe.md
Raw file servicenow.com

Set up SAFe related configuration in Azure DevOps projects and understand the workflow of SAFe PI and Sprint integration with Azure DevOps.

After creating map configuration for SAFe entities, import areas, teams, and iterations for your Azure DevOps projects and update the following fields. These fields are mandatory if Sync Sprints is set to true.

  • ART: Select an agile release train (ART).

  • ART Iteration Path: Select an iteration that is an equivalent to the parent of PI.

    Note: If the ART Iteration Path lookup ([Omitted image "lookup_icon.png"] Alt text: Lookup icon) does not return any records, import areas, teams, and iterations from Azure DevOps and try again.

    For the example shown in the following screenshot, Fabrikam must be selected as the ART Iteration path.

The application will then automatically identify PI 1 as the program increment. Sprint 1, Sprint 2, and so on, are identified as the corresponding SAFe sprints in the ServiceNow instance.

[Omitted image "safe-pi-sprint.png"] Alt text: Azure DevOps SAFe project example.

Important:

  • To create team integration settings for a project, the SAFe teams must be a part of the project's ART.
  • All teams of an ART must share the same sprint cycle.

SAFe sprint and PI integration workflow

[Omitted image "SAFe-Sprint-ADO-Import-Sprints.jpg"] Alt text: Import Sprints workflow between SAFe and Azure DevOps.

Search documentation
Search document titles and file paths on the australia branch