Old boards

To manage your issues and projects in Tracker, you can use Agile tools and methodologies: issue boards, sprints, burnout charts, and planning pocker.

Agile development methodologies were created for managing software development processes. Nowadays, they are successfully employed in a variety of domains. There are various agile development approaches, such as Scrum and Kanban.

For more information, see Basic concepts of agile development.

Issue boards in TrackerIssue boards in Tracker

In Tracker, agile tools are grouped on issue boards.

Managing issue boards in Tracker is similar to working with a regular sticker board. Use boards of different types to plan and track your Agile workflow:

• Basic boards allow you to arrange issues in columns based on their status.

• Scrum boards allow you to display statuses and offer sprint management tools, issue estimation, and burn down charts.

• Kanban boards are similar to basic boards, but all issues with the Open status are automatically moved to the Backlog column.

For more information about working with an issue boards:

• Creating a board in Tracker
• Working with a Tracker agile board
• Sprints
• Collaborative workload estimation
• Burndown charts

Basic concepts of agile developmentBasic concepts of agile development

Tracker uses the following terms and concepts from the Scrum methodology:

Backlog

List of issues or product requirements that must be completed in the project. Backlog issues are usually sorted by priority.

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 using cards, where team members each rate complexity in story points.

Issue 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 as the issue status updates.

Burndown chart

Chart that shows how fast planned issues are completed 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. You can use Story issues to group any issues based on a common topic in Tracker.

Story point

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 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. You can use epics to group any issues based on a common topic in Tracker.

Sub-epic

Issue that is included in an epic.