> 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/daily-expectations-of-tech-fleet-observers/pick-projects-to-observe.md).

# Pick Projects to Observe

## Picking projects

You should pick one project to observe, and you should observe that project for one entire sprint. 

You should also get a variety of observations in meetings from different projects, because every project carries out its work differently. No two projects are the same, as it should be with [Agile teams](/agile-training-portal/agile-handbook.md)! 

## Knowing which projects are live

Check out the new Observer Dashboard to see all of the live projects, and all of the information about them!

{% content-ref url="/pages/fKQU2Lmxdwlc2ho9aetm" %}
[Observer Dashboard](/observer-portal/observer-dashboard.md)
{% endcontent-ref %}

## 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/daily-expectations-of-tech-fleet-observers/pick-projects-to-observe.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.