MoSCoW Prioritization

The MoSCoW method for prioritizing features: Must have, Should have, Could have, Won't have.

Syntax

design-and-specify

Must:  Product fails without this
Should: Important, workaround exists
Could:  Nice to have, low impact if cut
Won't:  Out of scope for this release

Example

design-and-specify

// Feature: Blog Platform v1

MUST HAVE:
  - User registration and login
  - Create and publish blog posts
  - Read posts (public, no auth required)

SHOULD HAVE:
  - Tags and categories
  - Featured image per post
  - Author bio on post page

COULD HAVE:
  - Social sharing buttons
  - Reading time estimate
  - Related posts section

WON'T HAVE (v1):
  - Multiple authors / team blog
  - Subscriptions / email newsletter
  - Comments (will evaluate for v2)