Product Backlog Items
The product backlog is composed of backlog items, which I refer to as PBIs, backlog items, or simply items (see Figure 6.2).
Figure 6.2. Product backlog items
Most PBIs are features, items of functionality that will have tangible value to the user or customer. These are often written as user stories (although Scrum does not specify the format of PBIs). Examples of features include something brand-new (a login screen for a new website), or a change to an existing feature (a more user-friendly login screen for an existing website). Other PBIs include defects needing repair, technical improvements, knowledge-acquisition work, and any other work the product owner deems valuable. See Table 6.1 for examples of the different types of PBIs.
Table 6.1. Example Product Backlog Items
PBI Type |
Example |
Feature |
As a customer service representative I want to create a ticket for a customer support issue so that I can record and manage a customer’s request for support. |
Change |
As a customer service representative I want the default ordering of search results to be by last name instead of ticket number so that it’s easier to find a support ticket. |
Defect |
Fix defect #256 in the defect-tracking system so that special characters in search terms won’t make customer searches crash. |
Technical improvement |
Move to the latest version of the Oracle DBMS. |
Knowledge acquisition |
Create a prototype or proof of concept of two architectures and run three tests to determine which would be a better approach for our product. |