mvp-scoping

To define MVP scope, state your hypothesis, enumerate candidate features, apply MoSCoW prioritization, and set a cut line to separate v1 shippable items from deferred ones. This prevents overbuilding by constraining the plan to minimal, shippable features.

MoSCoW prioritization separates features into Must Have, Should Have, Could Have, and Won't Have categories. In MVP planning, it helps distill a full vision into a minimal v1 scope by clearly defining what ships now and what stays deferred.

Create an MVP spec by stating your hypothesis and success signals, enumerating features, applying MoSCoW prioritization, assessing risks, and defining a clear cut line. This structured process outputs a concise, ready-to-implement plan for v1.

Yes, you can scope an existing feature spec. The process takes your idea or feature spec and distills it into a minimal, shippable plan within a given timeline by applying hypothesis definition, feature enumeration, and MoSCoW prioritization.

The best way to cut features is defining a clear cut line after MoSCoW prioritization. Items below the cut line become Won't Have features, staying deferred with specific triggers for future implementation, ensuring the MVP remains minimal.

MoSCoW prioritization may not suit product management scenarios lacking a clear hypothesis or defined timeline. It requires candidate feature enumeration and success signals to effectively constrain scope and produce a ready-to-implement MVP plan.