Product Backlog
A prioritized queue of user-focused needs that the team owns and continually updates for the product.
Key Points
- Single, authoritative source of upcoming product work.
- Ordered by value, risk, and dependencies so the most important items appear first.
- Continuously refined as feedback emerges; items gain detail, estimates, and acceptance criteria as they rise.
- Product owner manages content and ordering; the delivery team collaborates to refine and estimate.
Example
A mobile banking team maintains a product backlog with items such as "As a customer, I want to deposit checks by photo so I can avoid visiting a branch." The product owner orders these items by value and risk. High-priority items near the top have clear acceptance criteria and estimates, making them ready for the next sprint.
PMP Example Question
A team wants a single, prioritized source of all user-centered requirements for a product that is updated continuously as feedback arrives. Which artifact should they use?
- Sprint backlog
- Product backlog
- Project management plan
- Release burndown chart
Correct Answer: B — Product backlog
Explanation: The product backlog is the prioritized, evolving list of user-focused work maintained for the product; the other options serve different purposes.