prioritization-advisor-re
Installation
SKILL.md
Purpose
Guide requirements engineers in selecting and applying the right prioritization technique. Use this when stakeholders cannot agree on what matters most and you need a structured method to force real trade-off decisions.
This is not about managing a backlog. It is about establishing relative priority among requirements so that when resources are limited (they always are), the team builds the right things first.
Key Concepts
Prioritization Techniques Overview
| Technique | Scale | Best For | Effort | Stakeholders |
|---|---|---|---|---|
| In/Out | Binary | Quick scope decisions, release planning | Very low | Any number |
| Three-Level | H/M/L with rationale | Small to medium requirement sets | Low | 1-5 |
| MoSCoW | Must/Should/Could/Won't | Timeboxed releases, agile projects | Low | 1-10 |
| Pairwise Comparison | Relative ranking | Small sets (< 20) where order matters | Medium | 1-3 |
| $100 Allocation | Relative weighting | Group consensus, revealing hidden priorities | Medium | 3-10 |
| Value/Cost/Risk | Scored spreadsheet | Data-driven decisions, large sets | High | 3+ stakeholders + estimators |