# Prerequisites

* Use **Jira** Cloud, Jira Server (> 7.8.0) or Jira Data Center (> 7.8.0).
* Use a **two layer deliverables structure** composed of epics (called “features” in the application), and underlying tickets (stories, spikes, bugs, tasks …). Sub-tasks and sub-bugs can also be used by teams, but will not be visible on the program planning board.
* When using the **Jira Cloud** platform: we only support ‘**company-managed**’ (‘Classic’) Jira projects. The ‘team-managed’ (‘next-gen’) are not supported, as they don’t support the necessary functionality to collaborate between teams. ([more info](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-jira-service-management-next-gen-projects/))
* Work **iteratively** in periods (called “Program Increments” or “PI” in **SAFe®** terminology) at program level. ([more info](https://ativo.io/docs/period-setup/))
* Teams can work using a **Scrum** or **Kanban** methodology.
* Teams can use **Story Points** or **Man Days** for their estimations, or use **no estimations** at all.
* Teams should use the same **cadence** (sprint start and end dates) within the same PI. There is a tolerance of 2 days for teams starting a bit earlier or later.
* The application is displayed in **English only** (contact support for upcoming language support).


---

# Agent Instructions: 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:

```
GET https://docs.ativo.io/getting-started/prerequisites.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.