# Project Team Functions

## Definition

A job function is the title that someone calls themselves. These can vary from company to company. 

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FyyEZURl5vREizkDWBPWm%2Fduties.png?alt=media&#x26;token=1fe42170-88f4-4c23-9c84-3931f29e7d1d" alt=""><figcaption></figcaption></figure>

Learn more about how the job function works on an agile team here:&#x20;

{% content-ref url="../../../team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams" %}
[commitment-vs.-job-function-vs.-people-on-teams](https://guide.techfleet.org/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams)
{% endcontent-ref %}

## Functions are Fluid on Cross-Functional Teams

Teams who are cross-functional do not work in "departments" isolated. They co-work with each other and involve each other in the work constantly. Researchers do design; product people do research; designers do development. Teammates commit and decide themselves how they want to get involved with a deliverable called a RACI chart. Check out the Agile Handbook for more information about how team functions work on cross-functional agile teams:&#x20;

{% content-ref url="../../../agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork" %}
[cross-functional-agile-teamwork](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork)
{% endcontent-ref %}

{% content-ref url="../../../agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/daily-life-on-agile-teams" %}
[daily-life-on-agile-teams](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/daily-life-on-agile-teams)
{% endcontent-ref %}

{% content-ref url="../../../agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts" %}
[raci-charts](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts)
{% endcontent-ref %}

## How it Relates to Other Components

The job function is what people call themselves, and they decide which [duties](https://guide.techfleet.org/project-portal/project-success-handbook/project-components/project-duties) and [deliverables](https://guide.techfleet.org/project-portal/project-success-handbook/project-components/project-deliverables) they want to play a role in together. This gets decided [every week](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team), or every iteration, depending on the Agile Method you have chosen for your team (see about methods [here](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-methods)).

## Examples of Project Team Functions

Here's a dashboard showing the different kinds of team functions that perform different duties.

{% embed url="<https://airtable.com/appMDxpNsGN2qyS8N/shroOCNmDNFu7QpTM>" %}

## Head to the Next Lesson