HKSM

A Prioritized Product Backlog is a single, consolidated source of requirements that sets project scope by listing product or service features in ranked order for delivery.

Key Points

• Acts as the single source of scope, capturing all product requirements as backlog items.
• Items are ordered by value, risk, urgency, and dependencies so the most important work is done first.
• Continuously refined by adding detail, estimates, and acceptance criteria as understanding increases.
• Owned by the product owner, informed by stakeholders and the team, and distinct from the sprint backlog.

Example

A team building a mobile banking app maintains a Prioritized Product Backlog with items like login, balance view, and fund transfer. After ranking by customer value and risk, the first release includes secure login and balance view, while lower-priority features are scheduled for later sprints. Stakeholder feedback leads to reprioritizing the transfer feature higher for the next iteration.

PMP Example Question

Which artifact defines scope in an agile project by serving as a single, continuously ordered list of features to be delivered?

1. Prioritized Product Backlog
2. Sprint Backlog
3. Requirements Traceability Matrix
4. Work Breakdown Structure

Correct Answer: A — Prioritized Product Backlog

Explanation: The Prioritized Product Backlog is the single requirements source that orders features by priority, thereby defining and guiding project scope in agile.