Minimum marketable feature (MMF)
A minimum marketable feature is the smallest increment of functionality that delivers real user value and could plausibly be released to customers as a standalone improvement. Unlike an MVP (a learning experiment), an MMF is a real release; unlike a full epic, an MMF is decomposed to the smallest releasable slice.
The MMF concept comes from the Lean and SAFe literature as a counter to two failure modes: shipping half-features that don't help anyone (because the slice was vertical but too thin) and waiting months to ship a full epic (because the team wouldn't decompose). A well-formed MMF passes a 'would a real user notice and benefit?' test, even if the surrounding feature is incomplete. The skill is in slicing: SAFe teams often use story mapping and the INVEST criteria to find MMF-sized slices inside larger features. Shipping 4-6 MMFs per PI is healthy; shipping 1-2 'full features' per PI almost always signals slicing failure.
Related terms
- Minimum viable product (MVP)
A minimum viable product is the smallest version of a product that lets the team test a specific hypothesis with real users — not a beta, not a stripped-down v1, but a deliberate experiment whose only job is to produce learning.
- Vertical slicing
Vertical slicing breaks work into thin slices that cut through every layer of the architecture — UI, business logic, data, infrastructure — so each slice delivers end-user value independently.
- INVEST criteria
INVEST is a mnemonic — coined by Bill Wake in 2003 — for the qualities of a good user story: Independent (can be worked on without depending on other stories), Negotiable (not a rigid contract, room to discuss the implementation), Valuable (delivers value to the user or business), Estimable (the team can size it), Small (fits in a single sprint), Testable (acceptance criteria can be verified).