What Is a PBI in Scrum?

What Is a PBI in Scrum?

A Product Backlog Item (PBI) is a single, trackable unit of work in Scrum that captures a piece of value the product team intends to deliver. PBIs sit in the product backlog and are pulled into a sprint backlog once the team commits to them during sprint planning.

What Makes a Valid PBI

Not every task becomes a PBI. A valid PBI is typically small enough to be completed within a sprint, testable, and aligned with a clear user or business outcome. It should have a visible description, acceptance criteria, and an estimate of effort. Teams often use the INVEST heuristic — Independent, Negotiable, Valuable, Estimable, Small, and Testable — as a sanity check when writing PBIs.

PBI vs. Sprint Backlog Item

The distinction matters. The product backlog holds all PBIs; the sprint backlog holds the subset the team has selected for the current sprint. A PBI becomes a sprint backlog item once it is pulled in, but the reverse is not true. Only PBIs that have been refined, estimated, and agreed upon are ready for selection.

Common PBI Formats

Teams write PBIs in several familiar shapes:

• User story: "As a [role], I want [feature] so that [benefit]."
• Enabler: Technical or infrastructure work that supports future user stories.
• Bug fix: A correction that restores expected behavior.
• Spike: Time-boxed research or exploration to reduce uncertainty.
• Defect: A deviation from the definition of done that requires remediation.

Acceptance Criteria and Definition of Done

Each PBI should include acceptance criteria that define when it is complete. These criteria sit alongside the team's broader Definition of Done and give the product owner and developers a shared threshold for moving the item from "in progress" to "done." Without clear criteria, PBIs tend to linger across sprints and erode predictability.

Sizing and Estimation

Teams estimate PBIs using techniques like story points, T-shirt sizes, or ideal days. The goal is not precision but relative comparison: understanding which PBIs carry more complexity so the team can pull a realistic load into the sprint. A well-groomed PBI is estimable without being over-detailed.

Refinement as a Living Practice

Product backlog refinement keeps PBIs ready. During refinement sessions, the team breaks large items down, clarifies acceptance criteria, and re-estimates. This continuous activity ensures the backlog stays ordered by value and that the next sprint can begin without a bottleneck in preparation.