Export (0) Print
Expand All

Create your backlog

Creating a backlog helps you define the work that needs to be done. Once you have a backlog, you can use it to help manage when that work gets done, as well as associate items on the backlog with check-ins, acceptance tests, or other criteria.

  1. If your team doesn’t have one, set up your team project now. If you do have a team project, but you don’t have access to it, get invited to the team.

  2. Open the backlog page from Team Web Access or Team Explorer. For example, the Fabrikam, Inc. team navigates to http://fabrikamprime:8080/tfs/DefaultCollection/Fabrikam%20Fiber%20Website/_backlogs.

    Open your team's backlog page
  3. Create a backlog item. Enter a title and add the item.

    Add an item to your product backlog

    Different backlog item types appear with different colors, to help you distinguish them at a glance. For example, bugs show as a different color than backlog items.

    Different types have different colors

    Want to create a portfolio backlog instead? Work with portfolio backlogs

  4. Highlight an item in the list, and then add another item. It will be added where focus is in the backlog, which is indicated by a line.

    The green line shows where the item will go.

    You can move the focus in the backlog with the up and down arrows on the keyboard, or with a pointing tool.

To change the order in which items are listed, you can drag them up or down within the list.

Reorder items in the list to show priority.

Now it is reordered.

The numbering changes to reflect the order.

To move an item in the list using the keyboard, hold down the Alt key and use the up and down arrows.

You can also move an item to the top of the list or specify a value to reorder within the list. 

Move to position

A: Yes. You can use Microsoft Excel or Microsoft Project to quickly create and update multiple work items.

A: From the backlog page, turn mapping on.

Toggle the mapping switch to enable or disable

Drop a backlog item onto a Feature in the mapping pane in order to add it.

Drag and drop, or select, shift focus to parent

To learn more, see Work with portfolio backlogs.

A: Check the area path and the iteration path of the item. Only backlog items assigned to the team’s default area path and under the default iteration path will appear in the team’s backlog. (You can use predefined queries or create queries on the Queries page to find missing backlog items.)

A: No, but when you set the item’s State to Removed, Closed, or Done, it no longer appears on the backlog. Also, you can change the item’s Area Path to remove it from your team’s backlog.

A: Depending on the work item type that appears on your backlog, you can open an item and provide an estimate of the Effort, Story Points, or Size required to complete it. For recommended best practices, see Estimating.

You can provide an estimate of work.

A: Objects used to track work vary based on the process template used to create your team project. If you use Visual Studio Scrum, you can create Product Backlog Items and Bugs with estimates in the Effort field. MSF for Agile Software Development supports creating User Stories with Story Points for the estimate. And, MSF for CMMI Process Improvement supports Requirements with Size for the estimate.

All three templates support tracking Features on the portfolio backlog. To learn more about the three process templates, see Work with team project artifacts, choose a process template.

A: Each of the backlogs serves similar but distinct purposes. The product backlog and portfolio backlogs contain high-level views of the stories, deliverables, features, or experiences that product owners want to track for the duration of a product release. Your product owner ranks the backlog items or deliverables in these backlog views and provides sufficient detail during the planning meeting so that your team can estimate and implement product backlog items.

In contrast, your team creates the sprint backlog, which contains the tasks to complete to finish backlog items committed for the sprint. In the product backlog, your team estimates the Effort, Size, or Story Points of backlog items. In the sprint backlog, your team estimates tasks, usually in hours or days. You do not need to create a sprint backlog in order to use the product and portfolio backlogs, but you will need to create a product backlog in order to create sprint backlogs.

Your product owner might update the product backlog every week, while your team might update the sprint backlog daily. Your product owner maintains the same product backlog throughout the project, but your team creates a new sprint backlog for each sprint.

The following table provides a comparison of each backlog's features.

Feature

Portfolio backlog

Product backlog

Sprint backlog

Level of detail

Less detailed

Less detailed

Very detailed

Mapping

Supported

Supported

Supported

Board type

Kanban

Kanban

Task

Add more backlog page views

Yes, see Add a backlog to Agile portfolio management

No

Yes, see Schedule sprints

Prioritize items on the page

Yes

Yes

No (items inherit priority from backlog)

Forecast

No

Yes

No

Filtering

Tags

Tags

N/A

Chart

Cumulative flow diagram

Cumulative flow diagram

Burndown, capacity

Duration

Project

Project

Sprint

Persistent

Yes

Yes

Yes

Show:
© 2014 Microsoft