Agile development tools

You can use various agile tools and methods to manage issues and projects in Tracker, such as issue boards, sprints, burn down charts, and poker planning.

Agile methodology was initially developed to manage the software development process, but it has since been applied to many other areas. There are several variations of agile methodologies, such as Scrum and Kanban.

To learn more about them, see Basic concepts of Agile development.

  1. Issue boards in Tracker
  2. Basic concepts of agile development

Issue boards in Tracker

In Tracker, agile tools are all grouped on the issue board.

Issue board

Managing Tracker boards is similar to working with a normal sticker board. Use different board types to manage your workload and monitor your progress with agile methodologies:

  • The Basic board lets you arrange issues in columns based on their status.

  • Scrum boards allow for status display just the same, but also offer sprint management tools, issue scoring, and burndown charts.

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

You can learn more about issue boards:

Basic concepts of agile development

Tracker uses terms taken from Scrum:

A list of issues or product requirements that must be completed in the project. Backlog issues are usually sorted by priority.
Project cycle, usually lasting 1-4 weeks. Each sprint focuses on developing a set of new product features and preparing them for release (an increment).
Poker planning
A method for collaboratively evaluating issue complexity using cards, where team members each rate complexity in story points.
Issue board
A 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
A chart that shows the completion speed of planned issues during a sprint as well as the amount of work remaining.
User Story
A “User Story” is a description of a feature that needs to be implemented in a product as a result of previous experiences or issues faced by users. A User Story is divided into standalone issues. You can use Story issues to group any issues based on a shared theme in Tracker.
Story point
A relative rating that describes effort needed to complete an issue. Usually a story point doesn't directly correlate with the number of work hours needed to solve the problem. The team rates issues collectively by comparing them to a simple task.
A larger feature or requirement that cannot be implemented within a single sprint. Epics are usually split into multiple User Stories or issues. You can use Epics to group any issues based on a shared theme in Tracker.
An issue included in an epic.