Building a backlog

You've set up your project and configured your systems. It's time to prepare the backlog of issues that your team will work from.

A backlog is simply a list of features, which could be for your product, service, project, etc. These features are not detailed specifications. Rather, they are usually described in form of user stories, which are short summaries of the functionality from a particular user's perspective. This is a common template for a user story: As a <type of user>, I want <goal> so that I <receive benefit>. For example, "As a developer, I want to log time against my tickets in the issue tracker during a sprint, so that I can show my progress."

Search the topics in 'Building a backlog':

Building a backlog in a Scrum project

In Scrum, it is critical to have a prioritized backlog, so the highest priority items are ready to be included in the next sprint.

The Backlog of your Scrum board is designed to help you manage this. You can quickly add, update, and rank issues on the board to build the backlog. When it's time to start work, pushing issues from your backlog into sprints is as simple as dragging and dropping.

Learn more: Using your Scrum backlog