Relative Prioritization Ranking

A straightforward ordered list of user stories arranged by importance. It is used to decide which stories should be included in each iteration or product release.

Key Points

  • Creates a single, ordered backlog where higher items are addressed first.
  • Helps select scope for upcoming iterations or releases based on value, risk, and dependencies.
  • Lightweight and easy to maintain; works well with evolving backlogs.
  • Relies on stakeholder input and product goals; ranking is relative, not absolute scoring.

Example

A product owner orders the backlog as: 1) Enable checkout with saved cards, 2) Add guest checkout, 3) Email receipt customization. During sprint planning, the team pulls the top items that fit capacity, ensuring the most valuable stories are delivered first.

PMP Example Question

A product owner uses a simple ordered list of user stories to decide which ones to include in the next sprint and upcoming release. What technique are they using?

  1. Weighted Shortest Job First (WSJF)
  2. Kano Analysis
  3. Relative Prioritization Ranking
  4. Planning Poker

Correct Answer: C — Relative Prioritization Ranking

Explanation: Relative Prioritization Ranking is a simple ordered list of user stories used to determine what to deliver in each iteration or release.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More