HKSM
Create Prioritized Product Backlog
This activity decomposes and clarifies Epics, then ranks the resulting work by value and other factors to form the project's Prioritized Product Backlog. The team's Done Criteria are also defined at this stage.
Key Points
- Breaks down Epics into smaller, clearer items (e.g., features or user stories).
- Orders backlog items by value, risk, urgency, and dependencies to guide delivery.
- Establishes the team's Done Criteria so completion is consistently understood.
- Produces a living backlog that is revisited and adjusted with stakeholder input.
Example
At project kickoff, the product owner and team take high-level Epics like "User account management," split them into stories such as "Create account," "Reset password," and "Two-factor setup," then rank these by business value and risk. They also agree on Done Criteria (code reviewed, unit tests passing, acceptance criteria met) before starting Sprint 1.
PMP Example Question
During early agile planning, the team breaks down Epics into user stories, prioritizes them by value, and agrees on Done Criteria. Which process are they performing?
- Create Prioritized Product Backlog
- Develop Project Charter
- Plan Scope Management
- Define Activities
Correct Answer: A — Create Prioritized Product Backlog
Explanation: This process refines Epics, ranks the resulting items to build the Prioritized Product Backlog, and sets the team's Done Criteria.
