In addition to the Team System Engineer, the Working Team consists of the so-called Nucleus Team: these are persons who work in this Team for a predominant part of their working time (> 80%), plus the Extended Team: these are persons who work in a few teams (between 20% and 80%).
Nucleus Team members sit and work together, coordinate their work in the Team Sync every day and have shared responsibilities as a team.
Extended Team members attend the Extended Team Sync (e.g. twice a week) and sit together with the Nucleus Team when necessary. This requires “slack” with regard to additional seats and workplaces in the team area. Extended Team members can work with a few Nucleus teams. The capacity that they provide for each team is planned at Cycle or Iteration level in the Team Calendar. The total capacity of each team member must never exceed 100%, ie if an Extended Team member is required more in one team, the capacity for other teams must decrease.
The members of the Nucleus and Extended Team make their work visible on the team’s team board (also called Kanban Board, Task Board or Scrum Board).
The following roles are not part of the Working Team:
Supporters work in their Service Team (team flovor “yellow”). They are visited by teams or visit teams on request. Supporters are usually planned by the Team Product Owner of the Service Team (Aka Service Owner) and usually have their work items as Backlog Items on their own team board.
Stakeholders are people who are interested in the team results but do not work within this team. For this reason, members of other teams can also be Stakeholders. Stakeholders participate in a team’s iteration review and provide open and transparent feedback.
Further suitable links:
| Events | Roles | Groups | Artifacts |
| Team Planning | Team Product Owner | Working Team | Team Backlog |