Use Agile methodologies
If your team's work is organized around Agile software development, it can be a good idea to try issue boards in Tracker. Boards help you keep track of tasks laid out for the team (such as during daily meetups). Issues are displayed on the board as cards sorted into columns based on their status.
If you chose to create a queue using the
Kanban templates, an issue board sharing the queue's name will also be created automatically. The board will display all issues contained in your queue.
You can also create multiple issue boards. This can be useful if you have multiple work groups or issue types:
On the top panel in Tracker, choose Boards → Create board.
Select the board type.
Enable the Add issues automatically option and set the filters so that only issues with the needed parameters are displayed.
For example, you can set up filters in such a way so that all issues from your queue are displayed on the board, or only issues with certain components or assignees are displayed, and so on.
Board types inTracker
Tracker has multiple board types:
Basic. This board has the least features, displays the team's issues and issue statuses.
Kanban. This board is similar to the basic board, but all issues with the Open status are automatically moved to the Backlog column.
Scrum board tools
Scrum board offers tools to help organize your workflow according to the Scrum methodology:
Scrum implies that your workflow is broken down into smaller cycles called sprints. A sprint usually lasts one or two weeks. Please try planning your sprints in a way that lets your team solve all scheduled issues in the allotted time. You should also gauge your issues with planning poker to visualize your workload more clearly beforehand.
Click Sprints in the upper-right corner of the issue board.
Create a sprint and set its start and end dates.
Add issues to your sprint: drag them from the Backlog column to the sprint issue list. Alternatively, you can specify a sprint in the Agile → Sprint field on the issue page.
If you want the board to only display issues related to a specific sprint, select that sprint at the top of the page. To track the issue completion speed for issues in a sprint, use a burn down chart.
To accurately gauge the workload for the upcoming sprint, you need to be able to evaluate its issue complexity. To do this, Scrum uses Planning Poker. This method lets each member of your team score issues on their complexity independently, discuss the results, and finally pin down the total score. This scoring method usually involves relative issue complexity grades called Story Points.
You can use planning poker in Tracker:
Burn down chart
The burn down chart shows the issue completion speed and remaining workload in a single sprint. Burn down charts are useful for evaluating whether the team will be able to solve the planned issues in time.
The chart's vertical axis shows the total workload left in Story Points, while the horizontal axis shows time. The ideal burndown chart should be as close as possible to a straight line that starts at the point with the most amount of work during the first day (total workload volume within a sprint) and ends at the zero point during the last day of the sprint.
To view the burn down chart in Tracker, click Burn down chart in the upper-right corner of the issue board.
Agile development strategies decompose issues as follows:
Larger tasks that cannot be completed within a single sprint are called Epics.
Epics are then broken down into
User Stories, which are finalized product features that can be implemented in a single sprint
User Stories are then broken down into standalone issues, such as designing the interface, or backend and frontend development.
To accommodate a system like that, the
Scrum queue template provides Epic and Story issue types. If you chose to create a queue using a template that does not have the Epic and Story issue types, you can add them in the queue settings.