csp-mvp-scopinglisted

# MVP Scoping Reduce a product idea to the smallest shippable increment that validates the core hypothesis. ## When to Use - You have a list of 10+ features and don't know where to start - A project timeline is slipping and scope needs to be cut - You're building a new product and need to define the first release - A stakeholder is pushing for "just one more feature" before launch - You want to validate a hypothesis with minimal engineering effort ## When NOT to Use - The product is already launched and this is an iteration (use sprint planning instead) - A compliance or security requirement is non-negotiable (those aren't scope — they're constraints) - The team has already agreed on scope and is in execution mode ## The MVP Scoping Framework ### Step 1: State the Hypothesis Write a single sentence: "We believe that [user] needs [capability] to solve [problem]. We'll know we're right when [measurable signal]." Example: "We believe that freelance designers need automated invoice tracking to reduce time spent on billing. We'll know we're right when 30% of beta users generate 5+ invoices in the first month." ### Step 2: List All Desired Features Dump every feature, nice-to-have, and "we should also" into a flat list. No filtering yet. ### Step 3: Classify Each Feature | Classification | Definition | MVP Decision | |----------------|------------|--------------| | **Core** | Without this, the hypothesis cannot be tested | Include | | **Enabling** | Required for core t