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 software development was initially designed 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.
For more information, see Basic concepts of agile development.
Issue boards in Tracker
In Tracker, agile tools are grouped on the issue board.
Managing Tracker boards is similar to working with a regular sticker board. Use different board types to manage your workload and monitor your progress with agile methodologies:
Basic boards let you arrange issues in columns based on their status.
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:
- How to create a board
- How to use the board
- Collaborative workload estimation
- Burn down chart
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).
- Planning poker
- 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.
- Burn down chart
- A chart that shows the completion speed of planned issues during a sprint and the amount of work remaining.
- User Story
User Storyis 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. In Tracker, you can use Story issues to group issues based on a common theme.
- Story Point
- A relative rating that describes the 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 can't be implemented within a single sprint. Epics are usually split into multiple User Stories or issues. In Tracker, you can use Epics to group issues based on a common theme.
- An issue that is included in an epic.