> 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/dashboards/burndown-chart-template.md).
# Burndown chart template
Easily set up a burndown chart with custom sprints, velocity tracking, and definition of done in dashboards. Visualize sprint progress and optimize agile project management.
When creating a sprint, you can now conveniently provide a title and description.
Once you set the start and end dates, the system automatically calculates the sprint's length, allowing you to see immediately if the selected dates are correct for 1-week, 2-week, etc., sprints.
You can set velocity which will be taken into an account once you build the burndown chart.
To properly display 'burned' points, ensure the default 'Points' field is added if it hasn't been enabled for the item yet on the template page.
Next, open project settings and under the 'Agile' tab, define the 'Definition of Done' for the item types used.
Once all settings are configured, navigate to the dashboard and click 'New Chart.' Then select 'Template' and choose the 'Burndown' chart.
Give it a title, select a project, and choose a sprint for the burndown chart. Save it.
Now you're all set.
---
# 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/dashboards/burndown-chart-template.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.
