Agile Teams

The Agile Teams capability allows for individual users to be grouped into dedicated teams and teams to be grouped within other teams. It also significantly reduces the amount of time account administrators and board administrators will need to spend on bulk user administration and new user onboarding.

Agile Teams are created and defined under the Teams section within Account Settings. Account Administrators and Team Organizers (new account role) have the ability to create and manage Agile Teams. Administrators can create, manage, and view all teams. Team Organizers can create and edit their own teams, but can't edit others' teams.

To access Agile Teams:

On the Home screen, go to Account Settings by clicking the gear icon  .This will take you to the Account Settings screen. Click the Teams tab:

At present all teams are public to the organization.

You would use the Enable/Disable toggle if, say, you're in the middle of doing some Admin work on a team and you don't want the team to be added to boards, but you don't want to lose their information. Thus you can disable the team, and after the team is built, you can enable it.

Planview AgilePlace supports a nested teams structure. For example, let's say that we have three teams: Engineering, Front-End, and Sparkles. The Engineering team could be the top-level parent team with Front-End as a child team and Sparkles could be a child team of the Front-End team. This means that if I assigned the Engineering team to the Lean/Agile Development board with role of User then the Front-End team and Sparkles team would inherit the User role on the Lean/Agile Development board. There are currently five levels of nested structure. 

To Update a team, click the team name and click Edit details to add individuals or teams, and change other team details. To add an emoji for the team, right click at the start of the team name and select an emoji from the list. Click Update Team.

When you click on a team, there are three views available:

• Overview - Displays a preview of members and boards for a given team.
• Members View - Shows all members (including other teams) for a given team.
• Board View - Shows all boards that a given team has access to with corresponding permissions. 

To assign boards to a team, click Overview > Add board (below).

On the subsequent Assign Board Access popup you can look up boards and assign board roles for teams.

When you add users and teams to a board, the highest permission wins. For example, if you assigned Amanda to a board with the role of Reader, but she's part of Team Alpha, which has a board role of User, Amanda would have User permission for that board because she is part of Team Alpha. If there's a discrepancy between team and user permissions a warning symbol will appear next the the user or team within the Members tab on a board. Additionally, role inheritance is displayed by a clickable connections icon on the Boards section of the Team page.

All teams are manually generated except the External and Everyone teams, which are system-generated and locked. User profiles have a new attribute called External user, where, if checked, the user will be added to the External team and removed from the Everyone team. You might use this in the case of external members and contractors, where you want to limit their access to a subset of boards, but want the access for everyone else in the organization to be open.