MVP Scope Definition

J

Jordan Reyes

@jordan-reyes

·

Define rigorous MVP scope with clear in/out decisions

28 copies0 forks
Share this prompt:
Define MVP scope for {{product_or_feature}}.

Vision: {{vision}}
Constraints: {{constraints}}
Target launch: {{target_date}}

Let me work through the MVP scope systematically:

**Step 1: Define the Core Value**
- What is the single most important thing this must do?
- What problem does it solve?
- For whom?

**Step 2: Identify Must-Have Features**
- What is absolutely required for the core value?
- What would make it unusable if missing?
- Apply the "would users pay for this alone?" test

**Step 3: Identify Nice-to-Have Features**
- What would enhance the experience?
- What could wait for v1.1?
- What are we tempted to include but should not?

**Step 4: Define Quality Bar**
- Performance expectations
- Reliability requirements
- UX polish level acceptable

**Step 5: Scope Statement**

| Category | In MVP | Out of MVP (v1.1) | Out of MVP (Later) |

**Step 6: Validate Scope**
- Can we build this in time?
- Does it deliver the core value?
- What are we trading off?

**Step 7: Success Criteria**
- How will we know MVP succeeded?
- What triggers the next phase?

Details

Category

Analysis

Use Cases

MVP definitionScope managementLaunch planning

Works Best With

gpt-4claude-3
Created Updated Shared

Related Prompts

Create your own prompt vault and start sharing