Let’s Get Started

The backlog is a collection of actionable, smaller items requirements that can be prioritized and bucketed into sprints or releases. For teams that practice Scrum, these are usually called User Stories and the idea is to break down larger projects into smaller units of requirements that can be built and shipped within a single sprint.

And that is the fundamental idea with our Backlog tool. Feature are effectively roadmap candidates (can also be thought of as Features or Projects), and the Requirements (eg User Stories) associated with the Feature all come together in this backlog, so you can prioritize against multiple Features and other things maybe not even be associated with a Feature, for a given Release (sprint).

Prioritizing the Backlog

Prioritizing the backlog is just an exercise in dragging individual Requirements (User Stories) into a stack-rank order, and optionally using Releases (sprints) to bucket them for when they’ll be worked on.

To prioritize the backlog:

1. Navigate to Backlog > Prioritize.
2. Add Requirements (user stories) as need to this list.
3. Drag Requirements (user stories) up or down to place them into priority order.

Release Activity

Activity tracking adds a dimension to the backlog. Whereas the backlog is used to prioritize requirements/user stories and organize them into releases, the Activity board makes it possible to view the state of items in a given release and easily update that status by dragging them across a Kanban board. See more details here.

To manage release activity:

1. Click the ‘Create Release’ icon button in the upper-right corner (flag icon).
2. Complete the modal form that appears for naming and placing the Release in your backlog.
3. Drag items from your backlog, into the release. See Release Management for more insights.