Product Backlog Item
A single, ordered unit of work or value recorded in a product backlog.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-backlog-item/
01What it means
A Product Backlog Item is an entry in the product backlog representing something needed to improve a product, such as a feature, defect, research task, or technical improvement. It is broader than a user story and becomes more precise through refinement.[1][2]
02Why it matters
A shared unit lets teams discuss, order, refine, and inspect work without pretending every item is a feature or that detail is known too early.
03When to use it
Use it in Scrum and backlog conversations where the item type may vary. Do not force every discovery question or strategic outcome into a delivery item.
04How it works
- Describe the need or opportunity.
- Make the item visible in the product backlog.
- Order it against current value, risk, and learning.
- Refine it as context improves.
- Select and verify it only when it meets the Definition of Done.
05A practical example
A team records a data-export reliability problem as a Product Backlog Item, then refines the symptoms, affected users, acceptance conditions, and operational risks before ordering it.
06Where it breaks
The item is a work representation, not proof of value or a complete requirement; excessive detail becomes waste as priorities change.
Common mistakes
- Using PBI as a synonym for user story.
- Writing items as an unvalidated feature inventory.
- Treating a refined item as a commitment to release.
07Sources
- The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
- Agile Workflow in Azure BoardsMicrosoft Learn · Official product documentationAgile Workflow in Azure Boards