What is Minimum Marketable Feature (MMF)?

A Minimum Marketable Feature (MMF) is a small, coherent capability that provides enough value to justify delivering it to users. It is useful when deciding how to divide a larger product change into meaningful slices.

Why it matters

It helps teams choose a useful slice of delivery rather than splitting work into technical pieces that users cannot benefit from.

How it works

Define the user need and the complete experience needed to address it. A marketable slice may require changes across several technical components, plus documentation, support, or operational readiness.

Choose a slice that users can benefit from and the organization can responsibly deliver. 'Minimum' refers to a useful boundary, not the smallest technical task.

An MVP is chosen primarily to learn about important assumptions. An MMF is chosen primarily as a useful capability to deliver. A particular piece of work may support both purposes, but the distinction helps make the intent clear.

Example

Imagine customers of an existing booking service must call support to reschedule appointments. The team defines a small, complete capability: customers can choose another available time, confirm the change, and receive an updated notification. It includes the necessary capacity checks and handling of appointments that cannot be changed online. The team deliberately leaves broader calendar redesign for later. After release, it examines successful rescheduling, support contacts, and scheduling errors. This is marketable because the whole customer task works and offers recognizable value. A button without the supporting journey would be smaller, but would not provide that capability.

Common misunderstanding

The smallest technical component is not necessarily the smallest useful capability. A payment API by itself does not let a customer complete a purchase if the interface, error handling, and operational support are missing. Splitting work along technical boundaries can produce many completed items with little usable value.

Define the end to end need and what makes the slice responsibly deliverable. Marketable value may include time saved or risk reduced, not just revenue. Distinguish that delivery purpose from an MVP chosen primarily to test an important assumption.

Related terms

Minimum Viable Product (MVP) · Outcome-Based Planning · Iterative Development

Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.