> 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/knowing-when-youre-ready-to-finish-observing.md).

# Knowing When you're Ready to Finish Observing

## Here's a check list you can use to guide yourself:

1. Have you watched the same team for one entire sprint cycle? 
2. Have you seen all the common sprint meetings like:
   1. Sprint standup
   2. Sprint planning
   3. Sprint demo
   4. Sprint retro
3. Have you witnessed people working together in different roles?
4. Have you witnessed working sessions for the role you desire to train in?
5. Have you witnessed challenges in team work? 
6. Do you feel more confident in what you will be expected to do on a Tech Fleet project training team as it relates to Agile work? 

## 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/knowing-when-youre-ready-to-finish-observing.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.