PromptsHub
Used by 5,000+ developers & creators
Back to Business & Startups
Business & Startupsmvp-scopeproduct-managementagile

MVP Feature Prioritization and Scope Definer

Translates a broad product vision into a highly prioritized, buildable Minimum Viable Product scope using the MoSCoW framework.

Use Case

Use this prompt when you have a massive list of product ideas and need to aggressively strip away non-essential features to launch your product quickly and cheaply.
AI Prompt
Act as a Chief Product Officer and Agile Product Manager. I have a broad vision for a new startup product, but I need to narrow it down to a fast-to-build, budget-friendly Minimum Viable Product (MVP). Help me prioritize features using the MoSCoW methodology (Must have, Should have, Could have, Won't have for launch). Also, suggest a timeline and release strategy to get this MVP built within a 6-week development cycle. Here is my product concept: Overall Vision: [insert product vision, e.g., An AI-assisted project management tool for creative agencies], Desired Feature List: [insert features, e.g., real-time chat, automatic task delegation, invoicing, Gantt charts, file proofing, integrations with Slack and Figma, AI summary reports].

How to Use

  1. 1Input your overall product vision and your current messy list of desired features into the placeholders.
  2. 2Submit the prompt to receive a prioritized MoSCoW matrix and week-by-week development roadmap.
  3. 3Use this scope document to align your software developers and design team on what to build first.

Example Output

Must Have features for launch are automatic task delegation and file proofing, as these solve the core creative agency bottleneck. Should Have features are real-time chat and Figma integration, which enhance collaboration. Could Have features are AI summary reports and Slack integration, which can wait until after initial user feedback. Won't Have features for launch are invoicing and Gantt charts, as they add unnecessary complexity. Week one and two should focus on core database architecture and file uploading. Week three and four will focus on task delegation algorithms and visual proofing interfaces. Week five is for testing and bug fixing, followed by a public launch in week six.