> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/agile-board-1/scrum-board.md).
# Scrum board
SCRUM Board: Track sprint progress, manage tasks, and visualize team workflows efficiently within the desktop client Agile Board for streamlined project management.
In the scrum board, you see all the artefacts of your aqua sprint. You can set your elements to a different status via drag and drop. The possible status transfers are highlighted. If a transfer is not possible, this may be due to various issues:
| **Workflow is Activated** | **Workflow is Deactivated** |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
|
• The target status cannot be reached by the current status
• The target status is defined in another aqua artefact
• The target status requires fields which have to be set before changing the status
• You don't have the permission to set the status
| • The target status is defined in another aqua artifact |
|
|
|
If an element is set to a ***Definition Of Done*** status, you receive a green hint that the element is done. This has an impact on the burn down chart.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aqua-cloud.io/documentation/desktop-client/agile-board-1/scrum-board.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
