A minimum viable product (MVP) is a scaled-down version of software with essential features. It gives users something to try so a team can gather feedback and test its assumptions before adding more features. section 10.1.4
An MVP can also help manage expectations before launch. Sharing an early draft gives customers and team members a chance to respond, while helping developers refine their estimates of the work ahead. An early version does not remove the need for security assessments, compliance checks, or stakeholder signoff before release. section 11.3.3 section 10.1.4
Choosing what to defer
Suppose a team reviews 12 requested features and finds that the estimated work exceeds its quarterly capacity by 106 days. Negotiating which less-critical features to defer brings the commitment closer to what the team can deliver. An early draft can then help test expectations rather than leaving surprises until launch. section 11.3.3
At a small startup, a team may first build a minimal iterable product and use rapid feedback from sales, marketing, and product colleagues to work toward an MVP. That speed may involve quality trade-offs that need cleaning up later; it is a choice to make consciously, not a reason to ignore release checks. section 10.1.5 section 10.1.4
