# Daily Life on Agile Teams

## Video Version

{% embed url="<https://youtu.be/RjqUTMCPRLg>" %}
Credit: Tech Fleet <https://youtu.be/RjqUTMCPRLg>
{% endembed %}

## Cross-Functional Agile Team Structure

 How are Agile Teams Structured? It depends!

The team who is [cross-functional in their nature](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork) brings many background and perspectives. They get together and build a consensus in what they will be responsible or accountable for, together as they agree to work week-to-week.&#x20;

They don't stick within these boundaries either: they live a cross-functional lifestyle where they can float across responsibilities and functions for the purposes of learning.

You should never hear teammates say "That's not my job, that's their job" on an Agile team.

You should hear teammates say, "I was hired for research but this week I want to get into product strategy!"

Your team may have job titles, but their duties vary and may fall outside of those titles. Everyone should be celebrating and encouraging this kind of environment for all of the reasons we talk about regarding making [strong Agile teams](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams).&#x20;

The more your team collaborates across functions:

1. The quicker they will get to Performing stage.
2. The more they will all "self-heal" from team conflict.
3. The stronger your self-organization becomes.
4. The stronger your continuous improvement becomes.

## Functions Are Not Roles

The title you have doesn't mean that you only do that kind of work on a cross-functional team.&#x20;

If you operate with different responsibilities, it does not mean you have multiple job titles.

A title is the function. A role is not a function. A role is a set of responsibilities that you agree to on an Agile cross-functional team.&#x20;

Learn more details about cross-functional functions, duties, and people here:

{% 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 %}

## Daily Life on Agile Teams

Let's talk about what day to day life looks like on Waterfall and on Agile cross-functional teams.

## Life on a Waterfall Team

It's more common that teams call themselves agile and they don't live in the agile philosophies.&#x20;

If you're building things on a waterfall team, this is what happens:

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FyIGu7jYyQeE3wRTlLpS9%2Fwaterfall%20daily%20life.png?alt=media&#x26;token=5e1972b3-0372-481e-bc0c-9e06f6bbfc61" alt=""><figcaption><p>Waterfall daily life on teams. Credit: Tech Fleet.</p></figcaption></figure>

**Everybody in the beginning of a project agrees to the scope before doing the work. Someone produces what's called a Product Requirements Document which outlines everything in scope for the whole project.**

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FCLUca5x2JsglpNzNbXEK%2Fclient%20to%20ba.png?alt=media&#x26;token=9b2d4c8d-29e0-469a-b97d-64dd8e5dbf14" alt=""><figcaption><p>Waterfall Client agreement to requirements phase. Credit: Tech Fleet</p></figcaption></figure>

**When the product requirements are outlined, each team works in phases. Every team function is working alone.  They meet alone, they talk alone, they decide alone. They don't communicate across functions. They don't collaborate across functions. They ship their work in silos to the next team.**&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FJgmakCnIad1RvmtynskT%2Fwork%20waterfall.png?alt=media&#x26;token=fdd86a53-2fbb-435e-8b94-2538369c0993" alt=""><figcaption><p>Waterfall research, design, and development phases. Credit: Tech Fleet.</p></figcaption></figure>

**When the project is finished, they ship it, and gather feedback from clients and users. When it may be too late!**

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FUzFz9ogRdi7eBeoRs2Uy%2Flaunch%20waterfa.png?alt=media&#x26;token=0fb5d003-8871-4396-8731-26bb1fa1df78" alt=""><figcaption><p>Waterfall launch phase. Credit: tech Fleet.</p></figcaption></figure>

## Life on an Agile Team

Life on an Agile team is the opposite of Waterfall teams.&#x20;

The teams are working together across functions in [cross-functional teamwork](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/cross-functional-agile-teamwork).&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2F7TZDbhCMUYjl4RFLMn9W%2Fagile%20daily%20life.png?alt=media&#x26;token=b842334e-fa51-45d6-af45-e9a46f3bac87" alt=""><figcaption><p>Life on Agile teams. Credit: Tech Fleet.</p></figcaption></figure>

**When they start the work, all functions rally to understand high level goals and outcomes to achieve.**

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FDCNOgeKEZAhZYEKGxPf7%2Fagile%20client.png?alt=media&#x26;token=6cf7baf7-3278-43f1-afd9-64005999cce3" alt=""><figcaption><p>Agile client intake. Credit: Tech Fleet.</p></figcaption></figure>

**Everyone collaborates across functions to gather the most important requirements to deliver first.**

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FDqDt12CmjGIWSEuDjifm%2Fagile%20requirements.png?alt=media&#x26;token=cf74fba2-311c-4c3a-81c5-c25075a4b132" alt=""><figcaption><p>Agile requirements. Credit: Tech Fleet.</p></figcaption></figure>

**Everyone collaborates to quickly deliver those requirements across research, design, and development. They check their work as they go with users and with clients.**&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FGd3qI5x7Ko9KEWbgjPqG%2Fagile%20iteration.png?alt=media&#x26;token=131d7408-2b91-49d0-9848-2b4f00e61d56" alt=""><figcaption><p>Agile cross-functional team work across functions. Credit: Tech Fleet.</p></figcaption></figure>

**They ship in usable, small chunks quickly, and gather feedback in order to pivot and refine their plans ahead.**

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FHxrve48ekVqgp37laHET%2Fagile%20results.png?alt=media&#x26;token=2c576941-4bd0-4901-98e6-54e1525ab3eb" alt=""><figcaption><p>Agile feedback loop. Credit: Tech Fleet.</p></figcaption></figure>

## 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/agile-training-portal/agile-handbook/agile-teamwork/day-to-day-on-an-agile-team/daily-life-on-agile-teams.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.