Loading...
Categorize requirements using MoSCoW (Must have, Should have, Could have, Wont have) for clear prioritization and scope management.
# 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]
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Helps you articulate a compelling, long-term product vision by guiding you through the creation of a 'Working Backwards' Press Release or a strategic memo.
Develops pricing models and strategies
Inspired by Jeff Patton's user story mapping approach, this template assists product teams in visualizing the user journey to create a shared understanding and prioritize features effectively. It presumes existing session context on segments, personas, and their narratives. If such context is lacking, the AI assistant is prompted to request it.