# Team Structure on Tech Fleet Project Training

## Team Structure

Project structure is set up as a cross-functional structure. [Learn more about cross-functional teamwork dynamics here](/team-portal/new-teammate-handbook/expectations-for-teammates/what-does-it-mean-to-be-a-cross-functional-teammate.md). 

Agile and empowered teams are all about sharing leadership and sharing decision making together.

Teammates share leadership with each other, and everyone makes decisions together in the ways of [self-organization](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization.md).

No one team member is "above" another lead or co-lead. Everyone pitches in to the work they want to commit to each week in sprint planning sessions through [RACI Charts](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts.md) and [Sprint Goals](/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items.md) activities. 

Teammates choose to [perform different duties and responsibilities](/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md) every time they prioritize work as a team. 

## Teammate Responsibilities

<figure><img src="/files/etDHaDbFH1JYf0Gv6rYr" alt=""><figcaption></figcaption></figure>

Each teammate is able to float across responsibilities as part of a cross-functional team. Each team position has daily expectations for responsibilities under each role they play.&#x20;

1. Project management function&#x20;
   1. Account management duties
   2. Project management duties
   3. Scrum master duties
   4. Product operations duties
2. Product strategy function
   1. Business analysis duties
   2. Product ownership duties
   3. Product management duties
   4. UX research duties
3. UX research function
   1. UX research duties
   2. UX strategy duties
4. UX design function
   1. UX design duties
   2. UX research duties
   3. UX strategy duties
5. UX writing function
   1. UX writing duties
   2. UX research duties
   3. UX strategy duties
6. Development function
   1. Front-end development duties
   2. Back-end development duties
   3. Solutions architecture duties
   4. QA duties

[See the full details of cross-functional duties here on our dashboard](/project-portal/project-success-handbook/project-components/project-duties.md) in the Project Success Handbook.

## Head to the Next Lesson


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/team-structure-on-tech-fleet-project-training.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.