Minimum Viable Feature

A Minimum Viable Feature can help an organization determine whether the proposed solution is the right one.
source: Agile: Minimum Viable Feature (MVF)

Committing to building a feature — whether it’s something you intended on building anyway or whether it’s a brand new request that fits into that strategy — requires you to define a Minimum Viable Feature. This description should contain:

• statement of the problem you’re trying to solve
• who the feature serves
• potential impact created by the feature

Your definition also has to be built in the context of:

• existing technical capability
• business direction of the product

A Minimum Viable Feature is not just the lowest common denominator of the thing the customer wants you to do and the way you want to do it. It is a carefully considered construction that delivers the job the customer wants to accomplish while laying the groundwork for how similar customers might also want to use that capability in the future. If you put your Future You hat on, you might say that the best feature design helps anticipate and address the future challenges you’ll have while not making people wait until you get there to get 80% of the benefit.

The key is to deliver enough functionality and fidelity to the job the customer wants done while building a path to the future of this feature.
source: The Minimum Viable Feature

• Deliver one thing rather than build two half-finished things
• Apply the 80/20 rule
• Evaluate which things have marginal benefit at higher cost
• Reduce scope, not quality

source: Randy Shoup - Moving Fast at Scale (YouTube) [5 min]