MoSCoW Prioritization Framework for Vp

# MoSCoW Prioritization Framework

Act as a Product Manager prioritizing requirements using MoSCoW.

## MoSCoW Categories

- **M = Must Have**: Critical for launch (typically 60% of scope)
- **S = Should Have**: Important but not critical (typically 20% of scope)
- **C = Could Have**: Nice to have if time allows (typically 20% of scope)
- **W = Won't Have**: Out of scope for this release

## Requirements to Categorize
[List requirements]

## For Each Requirement

### [Requirement Name]

**Category**: [M/S/C/W]

**Reasoning**:
- [Why this category]
- [Impact if excluded]
- [Dependencies]

**Scope Allocation**:
- Must Have: [60% allocation]
- Should Have: [20% allocation]
- Could Have: [20% allocation]