prioritization

# Prioritization

Systematically rank and prioritize requirements, features, backlog items, and initiatives using proven prioritization frameworks. Supports MoSCoW, Kano model, weighted scoring, and value-effort analysis.

## What is Prioritization?

**Prioritization** is the process of determining relative importance and ordering of items to focus resources on what matters most. Effective prioritization balances:

- **Value**: Benefit to customers or business
- **Effort**: Cost, time, and resources required
- **Risk**: Uncertainty and potential downsides
- **Dependencies**: Constraints and sequencing

## Prioritization Techniques

### MoSCoW Method

Categorical prioritization for timeboxed delivery:

| Category | Definition | Guidance |
|----------|------------|----------|
| **Must** | Non-negotiable, required for success | Without these, delivery is a failure |
| **Should** | Important but not critical | Significant value, workarounds exist |
| **Could** | Desirable if resources permit | Nice to have, enhances experience |
| **Won't** | Explicitly excluded this time | Not now, maybe later |

**When to Use:** Sprint planning, release scoping, MVP definition, timeboxed projects

**Rules:**

- Musts should be ~60% of capacity (leave room for unknowns)
- Won'ts are explicitly stated (not silently dropped)
- Categories are relative to the timebox, not absolute

### Kano Model

Customer satisfaction-based classification:

| Category | If Present | If Absent | Detection |
|----------|------------|-----------|-----------|
| **Basic (Must-Be)** | No increase in satisfaction | Major dissatisfaction | Customers assume these exist |
| **Performance (Linear)** | Proportional satisfaction | Proportional dissatisfaction | Customers explicitly request |
| **Delighter (Excitement)** | High satisfaction | No dissatisfaction | Customers don't expect |
| **Indifferent** | No impact | No impact | No reaction either way |
| **Reverse** | Dissatisfaction | Satisfaction | Segment prefers