Relative Prioritization

5 minutes 5 Questions

Relative Prioritization is a technique used to determine the order in which Product Backlog items should be addressed based on their value, risk, priority, and dependencies. By comparing items in relation to one another, the Product Owner can make better decisions about what to prioritize for the u…

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

A project team is preparing for a product MVP release. Given limited time and budget, the team needs to choose which features to prioritize. Which method should they use to prioritize?

Prioritizing features with the least dependencies. Using alphabetical order. Randomly selecting features. Using a relative prioritization metric, such as business value or cost of delay, and user value. Prioritizing features with the most constraints. Prioritizing features without regard to importance.

Correct Answer: Using a relative prioritization metric, such as business value or cost of delay, and user value.

Relative prioritization helps teams determine the most valuable features based on business value, cost of delay, and user value. Other methods do not help to prioritize according to these relevant factors.

Question 2

The product team is struggling to prioritize a list of 30 features that are not yet ranked by effort or value. In this situation, what approach should the team take?

Develop all features at once. Develop features starting with the least dependencies. Have the team individually rank all 30 features. Use the revenue generated by each feature as the sole criterion. Remove half the features to simplify the prioritization process. Use the MoSCoW method to classify features into Must-have, Should-have, Could-have, and Won't-have.

Correct Answer: Use the MoSCoW method to classify features into Must-have, Should-have, Could-have, and Won't-have.

The MoSCoW method helps to classify and prioritize features on a high level without considering value or effort. Other methods may result in an unbalanced prioritization or an overwhelming analysis.

Question 3

Your product development team is estimating the priority of several new features. Feature A has a high impact, high effort score, Feature B has a low impact, low effort score, Feature C has a low impact, high effort score. What is the best approach to prioritize these?

Rank Feature C first, Feature B second, and Feature A last. Rank Feature C first, Feature A second, and Feature B last. Rank Feature A first, Feature B second, and Feature C last. Rank Feature B first, Feature A second, and Feature C last. Rank Feature A first, Feature C second, and Feature B last. Rank all features equally.

Correct Answer: Rank Feature A first, Feature B second, and Feature C last.

Higher impact features should have higher priority. High impact, high effort (Feature A) should be prioritized before low impact, low effort (Feature B) and low impact, high effort (Feature C).

🎓 Unlock Premium Access

Agile Project Management + ALL Certifications

Relative Prioritization

Guide on Relative Prioritization in Agile Project Management

Agile Project Management - Relative Prioritization Example Questions

Question 1

Question 2

Question 3

🎓 Unlock Premium Access