Azure DevOps teams available in programs and projects
Introduction
What is Azure DevOps team configuration at program and project level? When you configure Azure DevOps teams at program or project level, the data exchange between Fortes Change Cloud and Azure DevOps is based on individual items from programs or projects, such as Features or User Stories. This is the alternative to portfolio-level configuration, where higher-level initiatives (Epics) are exchanged.
This article covers creating team configurations and adding teams that are selectable within programs and projects in FCC.
Who uses it?
- Administrators and integration specialists who configure the Azure DevOps integration at a more granular level.
- Program and project managers who work with Azure DevOps teams at the feature or work item level.
What value does it deliver?
- Enables fine-grained synchronization between FCC programs/projects and Azure DevOps at the level of individual work items.
- Gives program and project managers a live view of Azure DevOps team progress directly within FCC.
- Complements portfolio-level Azure DevOps integration for organizations that need synchronization at multiple levels.
How it works
Configuring Azure DevOps teams at program/project level works the same as at portfolio level: you create a team configuration and add teams, but the configuration is managed from the program or project instead of the portfolio. The result is that items from programs or projects (Features) are exchanged with Azure DevOps, rather than full initiatives (Epics).
Because the steps are identical, they are not repeated here. See Azure DevOps teams available in portfolios for the full instructions on:
- Creating a configuration (Application Link, Organization, Process, and field mappings in both sections).
- Adding a team (name, members for time registration, configuration, Project, Area Path, and optional Iteration Path).
The only difference is the level at which you start: open the ⋮ menu and Manage configurations at the program or project level where the information exchange should take place.
:::note Prerequisite An Azure DevOps application link must exist before you can create configurations or add teams at any level. :::
Choosing the level
| Level | Exchanges | SAFe term | Use when |
|---|---|---|---|
| Portfolio | Full initiatives | Epics | Whole initiatives are handed to Azure DevOps teams |
| Program / project | Individual items | Features | The connection is based on items from programs or projects |
Both levels can be used in the same environment when synchronization is needed at multiple levels.
FAQ
How is this different from configuring teams in portfolios?
The steps are identical; only the level differs. Program/project-level exchanges individual items (Features) instead of full initiatives (Epics).
Do I need a separate application link for this level?
No. The same Azure DevOps application link is reused; only the configuration and teams are created at the program/project level.
Can I combine portfolio-level and program/project-level integration?
Yes. Use portfolio-level for Epics and program/project-level for Features in the same environment.
Need more support?
For step-by-step instructions or troubleshooting, contact your Fortes Change Cloud administrator or consult in-app help.