bs-scope

Define MVP scope by applying MoSCoW prioritization to categorize features into Must, Should, Could, and Won't tiers. This process ties justification to validated hypotheses and produces a structured scope document with effort estimates to prevent scope creep.

Anti-scope in MVP milestone planning is an explicit list of excluded features with documented reasons. It is important because it removes ambiguity, enforces team alignment on what will not be built, and actively prevents scope creep during development.

Create a MoSCoW prioritization table by evaluating product features against validation goals, assigning them to Must, Should, Could, or Won't categories, and adding rough effort estimates using S, M, or L sizing to map delivery capacity.

Map validation goals to v0.2 and v0.3 milestones by aligning delivery cadence with risk mitigation. This approach structures incremental releases beyond the initial MVP build to test subsequent hypotheses and guide future development.

Document MVP exclusions by creating an anti-scope list with explicit reasons for each excluded feature. This prevents scope creep by establishing clear boundaries on what will not be built, reducing ambiguity and focusing development on validated hypotheses.

MVP scope generation relies on problem framing and market research inputs to decide the initial validation build. Without these inputs, the resulting MoSCoW prioritization and milestone definitions cannot be accurately justified against user hypotheses.