A product backlog is a prioritized list of features, fixes, improvements and tasks for a product, maintained by the product owner and refined continuously as understanding changes.
Why it matters
It is the single source of what the team may work on next. Keeping it ordered by value lets a team always start with the most important item, and regular refinement prevents surprises when work is pulled into a sprint. Backlog refinement, also called grooming, is the regular activity of splitting large items, adding detail and removing items that are no longer relevant.
Example
A backlog has 120 items. The top 10 are small, clearly described and ready to build. Items near the bottom are rough ideas. Each week the owner reorders the list after reviewing customer feedback and bug reports.
Common mistakes
- Letting it grow into a dumping ground that nobody reads.
- Leaving top items too vague to estimate.
- Treating every request as a commitment.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.