Priority Poker

What is Priority Poker?

Priority poker is a planning poker variant for ranking items by value instead of effort: participants privately score each item's importance, reveal together and discuss differences. It has no single standard rule set.

Updated November 2026 · 2 min read


Priority poker is a group prioritization technique that borrows the mechanics of planning poker but asks a different question. Instead of estimating how much effort an item will take, each participant privately picks a card showing how much value or importance they think the item has, everyone reveals at once, and the group discusses the differences before voting again. The result is a shared, relative ranking of features, requests or initiatives.

Unlike planning poker, priority poker has no single well-documented origin or standard rule set; teams and facilitators run it in several variations. What they share is the core idea that simultaneous voting reduces anchoring and groupthink, and that disagreements about value are worth surfacing before a roadmap is set.

Priority poker vs. planning poker

Planning pokerPriority poker
QuestionHow big is this?How valuable or important is this?
Typical participantsThe delivery teamProduct, business stakeholders, sometimes customers and the team
OutputRelative effort, usually in story pointsRelative value or priority score
Used forSprint and release planningRoadmap and backlog ordering

The two work well together. Dividing a value score by an effort estimate gives a simple value-for-effort ratio for ordering a backlog.

How to run a priority poker session

  1. Define "value." Agree on what participants are judging, such as customer impact, revenue, risk reduction or strategic fit. Without this, people vote on different things.
  2. Prepare a short list. Bring 10 to 20 items that are described well enough to compare. Long lists cause fatigue.
  3. Choose a scale. Many teams use the same modified Fibonacci cards as planning poker (1, 2, 3, 5, 8, 13, 20); others use a 1–5 scale.
  4. Present, vote, reveal. The item owner presents briefly, each participant chooses a card privately, and everyone reveals together.
  5. Discuss outliers. The highest and lowest voters explain their reasoning. Often one person knows about a customer commitment or a risk the others do not.
  6. Re-vote and record. Vote again if needed, then record the agreed score and the main reason behind it.
  7. Combine with effort. Pair value scores with effort estimates to produce a ranked list for the roadmap or backlog.

A hypothetical example

Consider a hypothetical customer-support software company choosing among four roadmap candidates. Product, sales, support and engineering leads vote on value; the engineering team has already estimated effort.

ItemAgreed valueEffortValue ÷ effort
A. Ticket merge1381.6
B. Saved replies search522.5
C. AI reply suggestions20201.0
D. Custom themes350.6

In the first round on item C, sales voted 20 while support voted 5, concerned that inaccurate suggestions would generate complaints. After discussion the group agreed on 20 but added a requirement for agents to review each suggestion. By ratio, the order is B, A, C, D. The team schedules B and A first as quick, high-return work and starts discovery on C, the largest bet.

Common pitfalls

  • No shared definition of value. If sales votes on revenue and support votes on ticket volume, the scores cannot be compared.
  • The loudest stakeholder wins anyway. The facilitator must protect the simultaneous reveal and give each outlier a fair hearing.
  • Treating scores as precise. A 13 versus an 8 is a judgment, not a measurement. Use scores to order items, not to justify them with false precision.
  • Ignoring effort and dependencies. High value alone does not make an item the next thing to build.

Priority poker is one of many product prioritization frameworks. Teams that want more structure often compare it with the RICE framework, MoSCoW prioritization or weighted shortest job first.

Frequently asked questions

What is the difference between priority poker and planning poker?

Both use private card choices and a simultaneous reveal, but they answer different questions. Planning poker asks how big an item is, involves the delivery team and produces effort estimates for sprint planning. Priority poker asks how valuable an item is, includes product and business stakeholders and produces value scores for ordering a roadmap or backlog. See planning poker.

How do you combine priority poker scores with effort estimates?

Divide each item's agreed value score by its effort estimate to get a simple value-for-effort ratio, then sort by that ratio. An item scored 5 for value and 2 for effort gives 2.5, which ranks above one scored 13 and 8, or 1.6. Large, high-value items with low ratios may still warrant discovery work before they are scheduled.