Collaborate using team resources
Within a team project, each team can work independently from other teams while still providing visibility on progress across the organization. When you’re familiar with the tools Team Foundation Server (TFS) provides to plan and track projects, you can use them to increase your team’s collaboration and productivity.
By default, when you create a team project, you also create a default team. For small teams, one team is all you need. However, for large organizations, creating additional teams provides each team with a view into their work, an ability to customize their task board, schedule their sprints, and customize their team home page.
A: Yes. When you add user accounts to a team project, you can add them as members of the team project, or you can add them to one or more teams added to the team project. If you work on two or more teams, you’ll want to make sure you, specify your sprint capacity for each team you work on.
Team members are also members of the Contributors group for a team project, which gives them access to work items and source code for the entire team project, unless they have been restricted. To learn how to restrict access, go here.
A: Both Team Web Access (TWA) and Team Explorer support quick context switching.
A: Most users who interact with TFS must have a Client Access License (CAL), which they get with Visual Studio or an MSDN subscription. However, you can provide access to stakeholders who have no CAL for the following activities:
Work Item Only View (WIOV): This view allows stakeholders to create and modify work items that they create using the Work Items page in TWA. In this view, stakeholders can report code defects, suggest a product feature, or further annotate their feedback responses. WIOV was designed specifically to provide access to any member in an organization with a TFS deployment who doesn't have a CAL.
Provide feedback: To allow your stakeholders to provide feedback, you must grant them specific permissions. You can also allow them to view their feedback responses or to create other types of work items.
View dashboards and reports: For stakeholders to view and refresh reports, you must assign them the required permissions. For stakeholders to view dashboards, you must assign them permissions to view the SharePoint site.
A: Yes. Although there is no concept of sub-teams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams.
A: Yes. If your organization has several teams that work from a common backlog and across many product areas, you might want to customize the team project to support team fields. This configuration will still allow teams to work independently, but work can be assigned to teams instead of by product area path.