Minimum Marketable Feature (MMF): Ship Value, Not Parts
An MMF is the smallest piece of functionality that provides real value to a customer. Use it to break down large projects into valuable, incremental releases. The footgun is confusing it with an MVP (for learning) or slicing it too thin to be useful alone.
WHY IT EXISTS: MMFs exist to combat the risk and delay of large, slow "big bang" releases. Instead of waiting months or years to ship a massive product, teams use MMFs to deliver value to users and the business incrementally, ensuring each small release is still meaningful and complete on its own.
THE MENTAL MODEL: An MMF is the smallest unit of functionality that provides recognizable value to a customer. Think of selling cupcakes. A customer wants a complete, frosted cupcake, not a bag of flour or a raw egg. The MMF is that single, finished cupcake—the smallest thing you can market and sell that a customer finds valuable.
HOW IT WORKS: You define an MMF by focusing on user outcomes, not technical tasks. Ask, "What is the smallest thing we can ship that solves a real user problem or completes a job for them?" This usually requires a full vertical slice of functionality: frontend, backend, and data persistence. An MMF must provide a coherent, end-to-end experience, however small its scope.
WHEN TO USE IT: MMFs are a primary tool for release planning and prioritization in agile environments. By breaking down large epics into a sequence of MMFs, you create a roadmap that delivers value consistently. This allows you to ship frequently, reduce the risk of large deployments, and get faster feedback from the market on complete, usable features.
WHEN NOT TO USE IT: Avoid the MMF label for purely technical tasks like refactoring or infrastructure setup, as they lack direct, marketable user value. More importantly, don't confuse an MMF with a Minimum Viable Product (MVP). An MVP's goal is maximum learning by testing a core hypothesis with minimal effort; an MMF's goal is delivering real, polished value with minimal scope.
ONE CANONICAL EXAMPLE: For a new e-commerce site, the epic is "Shopping Cart". An MMF is not "build the cart database table". A true MMF is "A user can add a single item to a cart and see it there." This is small, complete, and provides clear value. The next MMF might be "User can change the quantity of an item in the cart," followed by "User can remove an item from the cart."
Read the original → agilealliance.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.