---
metadata:
  - name: generator
    content: Diplodoc Platform v5.47.3
  - property: og:type
    content: article
  - property: article:section
    content: Без рубрики
  - property: og:title
    content: What is an Agile board
  - property: article:tag
    content: Navigation
alternate:
  - https://yandex.com.tr/support/tracker/en/manager/agile.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt


# What is an Agile board

Issue boards are a tool that helps you track and manage your issues in a streamlined manner. There are two types of boards in Yandex Tracker:

- **Basic boards** can be used by any teams and allow arranging issues in columns based on their status. [Creating a basic board](https://yandex.com.tr/support/tracker/en/manager/agile-create.md#basic).

- **With a backlog and sprints**: For teams that use [Agile methodologies](#sec_basics). [Creating a board with a backlog and sprints](https://yandex.com.tr/support/tracker/en/manager/agile-create.md#backlog-and-sprints).


## How to work with boards {#tips}

You can add no more than 2000 issues to the boards, so we recommend that you follow these guidelines:

* Only add issues to a board that you plan to complete in the near future (such as in the next six months).
* To avoid overloading issue boards, configure [automatic issue removal](https://yandex.com.tr/support/tracker/en/manager/agile-set-board.md#autodelete) so that issues in a specific status are removed from the board automatically.
* To review closed issues that were removed from the board, use the [issue search <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="16" height="16" class="g-icon" fill="currentColor" stroke="none" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 16 16"><path fill="currentColor" fill-rule="evenodd" d="M10 1.5A.75.75 0 0 0 10 3h1.94L6.97 7.97a.75.75 0 0 0 1.06 1.06L13 4.06V6a.75.75 0 0 0 1.5 0V2.25a.75.75 0 0 0-.75-.75H10ZM7.5 3.25a.75.75 0 0 0-.75-.75H4.5a3 3 0 0 0-3 3v6a3 3 0 0 0 3 3h6a3 3 0 0 0 3-3V9.25a.75.75 0 0 0-1.5 0v2.25a1.5 1.5 0 0 1-1.5 1.5h-6A1.5 1.5 0 0 1 3 11.5v-6A1.5 1.5 0 0 1 4.5 4h2.25a.75.75 0 0 0 .75-.75Z" clip-rule="evenodd"/></svg></svg>](https://tracker.yandex.com/issues) page. If you're using a **board with a backlog and sprints**, you'll see a link to a filter for the completed sprint's issues on the **Backlog** tab.
* To work with all of your issues (for example, to perform their general analysis through filtering or sorting), use queues: do not try to add all the issues to one board.


## Basic concepts of agile development {#sec_basics}

You can manage your issues and projects in Yandex Tracker using Agile tools and methodologies, such as issue boards, sprints, burnout charts, and planning poker.

[Agile development methodologies](https://yandex.cloud/en/blog/posts/2022/10/agile-and-project-management) were originally created for managing software development processes. Now, they are successfully employed a variety of domains. There are several Agile approaches that you can use. For example, [Scrum](https://en.wikipedia.org/wiki/SCRUM) and [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)).

Yandex Tracker uses the following [Scrum](https://en.wikipedia.org/wiki/SCRUM) terms and tools:

Backlog {#dlen_backlog}
:   A list of issues or product requirements that must be implemented in a project. Backlog issues are usually sorted by priority.

Sprint{#dlen_sprint}
:   Project cycle, usually lasting from one to four weeks. It is assumed that, under each sprint, a team should develop a set of new features (also known as increment) and make it release-ready.

Planning poker
:   Method for [collaboratively estimating issue complexity](https://yandex.com.tr/support/tracker/en/manager/poker.md) using cards, where team members each rate complexity in [story points](#dlen_sp).

Issue board {#dlen_board}
:   Board for tracking the status of issues in the current sprint. Columns on the board correspond to issue statuses. Cards with issue descriptions are pinned to the board and moved between [columns](https://yandex.com.tr/support/tracker/en/manager/agile-columns.md) as the issue status updates.

Burndown chart {#dlen_burndown}
:   Chart that [shows how fast planned issues are completed](https://yandex.com.tr/support/tracker/en/manager/burndown-diagram.md) during a sprint and the amount of work remaining.

User story
:   Description of a feature to implement in a product based on the previous experiences or problems faced by users. A user story is broken down into individual issues. In Yandex Tracker, you can use **Story** issues to group issues based on a shared subject. [How to use epics and user stories](https://yandex.com.tr/support/tracker/en/manager/epic.md)

Story point {#dlen_sp}
:   Relative rating that describes the effort needed to complete an issue. A story point unit is not usually measured in terms of man-hours. [The team rates issues collectively](https://yandex.com.tr/support/tracker/en/manager/poker.md) by comparing them to a simple task.

Epic
:  Large feature or requirement that cannot be implemented within a single sprint. It is usually broken down into several user stories or issues. In Yandex Tracker, you can use **Epic** issues to group issues based on a shared subject. [How to use epics and user stories](https://yandex.com.tr/support/tracker/en/manager/epic.md)

Sub-epic
:  Issue that is included in an epic.


#### Learn more

* [Basic tools](https://yandex.com.tr/support/tracker/en/manager/boards-instruments.md)

* [Creating a board](https://yandex.com.tr/support/tracker/en/manager/agile-create.md)

* [Working with a board](https://yandex.com.tr/support/tracker/en/manager/agile-set-board.md)

* [Board issues](https://yandex.com.tr/support/tracker/en/manager/agile-issues.md)

* [Board columns](https://yandex.com.tr/support/tracker/en/manager/agile-columns.md)