The Product Backlog Work Item
The Product Backlog Work Item has the following fields:
| Field Name |
Type |
Required |
Description |
| Title |
Text |
 |
Name for the Product Backlog item |
| Area |
Area Path |
|
Allows grouping of PB items into "Areas" that can be setup in the Team - Team Project Settings - Areas and Iterations menu |
| Release and/or Sprint |
Iteration Path |
|
Identifies the target Release and Sprint "Iteration Path" in which the Product Backlog item will be delivered. The Iteration Path
is setup from the Team - Team Project Settings - Areas and Iterations menu. When Release planning, a backlog item
can be allocated to a Release without specifying the target Sprint until the Product Owner and team can see far enough ahead |
| Estimated Effort |
Number |
|
The team's high level estimate for the effort to complete the backlog item in Story Points or days. This estimate should be more
accurate for backlog items that are likely to be worked on in the next couple of Sprints |
| Team |
List |
|
Assigns primary responsibility for a backlog item to a specific Team where running with multiple teams. Teams are setup with the
List Manager tab of the Team Project Portal |
| Business Priority |
Number |
|
Value of the Product Backlog item relative to its peers set by the Product Owner. By default Scrum for Team System will sort
queries on the assumption that higher values have greater priority |
| Delivery Order |
Number |
|
The actual delivery order set by the team after taking in to account the Business Priority and any technical considerations. By
default Scrum for Team System will sort queries on the assumption that higher values have greater priority |
| Work Remaining |
Calculated |
|
Provides the total work left (in hours) to complete a Product Backlog item. System calculated from the Work remaining fields of all
the linked Sprint Tasks for a given Product Backlog item |
| Current Status |
Workflow |
|
Tracks the status of the Product Backlog item, moving from Not Done - In Progress - Done - Deferred or Deleted. Many of the
state transitions are now automatic based on the state of the linked Sprint Tasks, for example the Product Backlog item will automatically
switch to "In Progress" as soon as a linked Sprint Task is set to In Progress |
| Description |
Tab/Text |
|
Typically in User Story format, this should be a paragraph describing the Product Backlog item in enough detail that
it is clearly recognisable. This is a place holder with enough detail to inform a detailed conversation with business
stakeholders or customer proxies, rather than a formal requirement specification |
| Conditions of Acceptance |
Tab/Text |
|
User Story format details for the conditions that need to be satisfied for this story to be fulfilled |
| History |
Tab/RO |
|
Shows the system generated change history of the Product Backlog item. The history data can be manually augmented by
the addition of text which itself becomes part of the change history |
| Links |
Tab/Links |
|
Normally used to view, add or remove links for the Product Backlog item to Sprint Backlog items, but can also be used to add
links to Source Control Changesets, Versioned Items, Test Results and Hyperlinks |
| File Attachments |
Tab/Files |
|
Used for attaching relevant documents to the Product Backlog item, for example a Visio workflow diagram to support the story |