Teams module
Introduction
You can group individual users into teams, which enables effort-based planning.
The team concept is used mainly in the Resources, Objectives, Gantt, Scope, and Board modules. However, since information about the team can be stored as a label or a custom field, it can also be displayed using the Gantt, Scope, or Risks module by adding it to the column view or card view.
You can quickly assign tasks to a respective team by inline editing in a column view in the Gantt, Resources, and Board modules.
You can create global teams and assign them to multiple boxes. Once created, you can easily convert them into box teams, which cannot be reassigned.
Features
The table presents the features available in the Teams module.
Feature | Description |
|---|---|
Team name | The BigPicture modules use a team name to identify teams. The team name is displayed with the team code in the Resources, Board, and Objectives modules to indicate the team's swimlane and the team picker's drop-down when configuring box-level teams. |
Team code is used to identify teams by the BigPicture modules and, when synchronized, by the host and connected platforms. | |
Link the team to its Jira board to quickly switch between different views. Based on this link, Bigpicture can auto-configure the sub-boxes scope synchronization and create sprints on the selected Jira board. | |
Team panel | The team panel contains three tabs:
|
User name link | A list of membership periods of a user (for a given team). |
Membership period | Your resources can be shared across different teams in the same period of time or can be fully allocated to a single team. This issue can be addressed using the memberships and availability of the team members. |
You can set the availability of each team member. The availability impacts the capacity, which is calculated as the difference between working hours specified in workload plans and non-working days. |