> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/observer-portal/observer-handbook/whats-a-tech-fleet-observer.md).

# What's a Tech Fleet Observer?

## All about Observing

Real-world Agile work can be very chaotic, and non-linear. School can teach you basics of theory about Agile but once you join Agile teams, the experience is very different. Tech Fleet leaves the door wide open for anyone in the world to watch Agile teams operate. 

In Tech Fleet, anyone can be an "Observer" and attend Tech Fleet project team meetings to observe, witness, or watch what is happening.  People do this as the first steps to joining projects as an apprentice or co-lead. This helps people see the real-world and watch people operate in Agile who are also learning it for the first time. 

There's no better way to learn how Agile teams operate than to watch them work. Every team works differently because they're always self-organized, making their own decisions as they go. As an observer you can watch how teams work in the real world without any extreme commitment. A lot of Tech Fleet members choose this route because it helps them build their awareness of apprenticeship life and helps them build confidence.

Tech Fleet has a long history of Observing. We opened this ability from day 1 in the community to remain inclusive even if people weren't selected on teams. People use this as first first training opportunity before they are a part of project training.

When applying for projects in Tech Fleet, co-leads and project coordinators prioritize people who have previously observed. 

While observing, you don't need permission to join meetings. You may simply watch, or you may be invited to participate in meeting activities or ask questions, but it is also fine to quietly watch and learn.

Read this entire Handbook to understand exactly how to get the most out of Observing in Tech Fleet. 

## The process of Observing

The process of Observing helps you prepare for real team work while doing project training in Tech Fleet. Here's the process in a diagram, and in text.

### The steps in picture form

<figure><img src="/files/fNMqDGNZLyWzGa4pDuw7" alt=""><figcaption><p>This picture shows the process of observing</p></figcaption></figure>

### The steps in text form

1. Read the Observer Handbook
2. Join Tech Fleet Discord
3. Get the Observers Role in Discord
4. Pick projects to observe
5. Observe teams working for 2 weeks
6. Reflect on your observations in Tech Fleet Discord channels

Get all of the details about these steps in this Handbook.

## Head to the next lesson:


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://guide.techfleet.org/observer-portal/observer-handbook/whats-a-tech-fleet-observer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.