The structure of the project teams is defined by a hierarchy of team areas. The team area manages team membership, roles assignments, and team artifacts.
- Defines the users (team members) on the team and specifies their roles.
- Defines the timeline in which the team is participating.
- Customizes the project process for the team.
Team areas are optional. A simple project with a small number of users might not need separate team areas. Instead, all work is done in the context of the project area.
Complex projects can have a hierarchy of team areas. Typically, one or more teams are assigned to each line of development. Users might have multiple assignments that require them to work on more than one team. Some project members, such as the project lead, might not belong to a team area, but are defined as members at the project level.
Team areas inherit the process and timeline of their parent, which can be the project area or a parent team area. They can customize the aspects of the process and when allowed, override all or portions of it.
Project work items belong to only one team area. Over time, a work item might be triaged to another team area within the project area.