prioritization-methods

# Requirements Prioritization Methods

Comprehensive guide to prioritization techniques for requirements and features.

## When to Use This Skill

**Keywords:** prioritization, priority, MoSCoW, Kano model, WSJF, weighted shortest job first, value cost risk, Wiegers, priority matrix, must have should have, delighters, basic needs, performance features, cost of delay

**Use this skill when:**

- Ranking requirements by business value
- Choosing between competing features
- Allocating limited development capacity
- Communicating priority decisions to stakeholders
- Balancing customer satisfaction vs implementation effort
- Making trade-off decisions in product planning

## Prioritization Methods Overview

| Method | Best For | Complexity | Stakeholder Input |
| ------ | -------- | ---------- | ----------------- |
| **MoSCoW** | Quick categorization, MVP scope | Low | Low |
| **Kano Model** | Customer satisfaction analysis | Medium | High (surveys) |
| **WSJF** | Agile/SAFe environments, flow optimization | Medium | Medium |
| **Wiegers' Matrix** | Quantitative value/cost analysis | High | Medium |
| **Opportunity Scoring** | JTBD-aligned prioritization | Medium | High (surveys) |

## MoSCoW Method

### Categories

```yaml
moscow:
  must:
    definition: "Non-negotiable for this release"
    criteria:
      - "System won't work without it"
      - "Legal/regulatory requirement"
      - "Core to value proposition"
    typical_percentage: "60% of effort"

  should:
    definition: "Important but not critical"
    criteria:
      - "Significant value, but workarounds exist"
      - "Key stakeholder expectations"
      - "Competitive parity"
    typical_percentage: "20% of effort"

  could:
    definition: "Nice to have if time permits"
    criteria:
      - "Enhances user experience"
      - "Low effort, incremental value"
      - "Differentiator but not essential"
    typical_percentage: "20% of effort"

  wont:
    definition: "Explicitly out of scope for now"
    crite