> 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/agile-training-portal/agile-handbook/start-the-agile-handbook-here/contents-of-the-agile-handbook.md).

# Contents of the Agile Handbook

1. There are six sections of the Agile Handbook:
   1. **Start Here** covers the importance of Agile.
   2. **Agile Philosophies** covers the mindset and traits of Agilists.
   3. **Agile Teamwork** covers how to mature and operate strong Agile teams.
   4. **Agile Methods** covers the Scrum method and other Agile methods of work.
   5. **Agile Deliverables** covers specific deliverables for Agile teams and for product development. 
   6. **Agile Glossary** is a community-created list of common terms you may hear in Tech Fleet related to Agile. 


---

# 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/agile-training-portal/agile-handbook/start-the-agile-handbook-here/contents-of-the-agile-handbook.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.