> For the complete documentation index, see [llms.txt](https://results.agilexr.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://results.agilexr.eu/1-guide-agile-teamwork-in-web-based-learning/chapter-1-agile-in-software/1.4-agile-mindset.md).

# 1.4 Agile Mindset

The idea of the Agile mindset has been a subject of conversation at many conferences and has been examined in numerous books. A helpful article on this topic from [Forbes](https://www.forbes.com/sites/stevedenning/2019/08/13/understanding-the-Agile-mindset/?sh=479bc6475c17) helps us understand what the Agile mindset is all about. It's important to mention that the term 'Agile mindset' was first introduced in 2010 by Ahmed Sidky, who is a well-known figure in the Agile community.

“Really, [Agile is a mindset](<https://medium.com/icAgile/the-Agile-mindset-5e8328452a23 >) — it’s a way of thinking — that’s defined by four values, described by twelve principles, and then manifested through an unlimited number of practices or different ways of working. It’s simply a deep understanding and culture of learning and experimentation and trying things out. Any creative work will benefit from this notion of an Agile way of working.” By: [Ahmed Sidky.](https://www.slideshare.net/AgileNZ/ahmed-sidky-keynote-Agilenz)

<figure><img src="/files/faEFVcnuq2TSs3tMRYrR" alt=""><figcaption><p><a href="https://medium.com/@AlphaApps/what-is-agile-bc4e7b62cb17">Being Agile by Ahmed Sidky </a></p></figcaption></figure>

*Disclaimer: Implementing the practices, tools and processes without the Agile mindset, values and principles of the Agile Manifesto is not Agile.*

\ <br>


---

# 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://results.agilexr.eu/1-guide-agile-teamwork-in-web-based-learning/chapter-1-agile-in-software/1.4-agile-mindset.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.
