prioritization-advisor

Choosing a prioritization framework requires evaluating your product stage, team context, and data availability to select methods like RICE, ICE, or Kano, preventing misapplication and framework whiplash.

RICE, ICE, and Moscow are distinct prioritization frameworks: RICE uses reach, impact, confidence, and effort; ICE is simpler; Moscow categorizes features by priority tiers. Selection depends on your team's data availability and decision-making needs.

To prioritize features with limited data, you can use simpler frameworks like ICE or Value vs. Effort, which rely on qualitative assessments and team consensus rather than requiring extensive quantitative metrics.

The Kano model is best for roadmap planning when you need to categorize features based on customer satisfaction, distinguishing between basic needs, performance, and delight, especially during product redesigns or maturity stages.

The best way to implement a prioritization framework for an agile team is to follow step-by-step implementation guidance, adapting the chosen method like RICE or Moscow to your team dynamics and addressing common pitfalls.

Prioritization frameworks fail when they are misapplied to the wrong product stage or team context, causing framework whiplash; selecting a method tailored to your specific decision-making needs and data availability prevents this.