Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Explaining MVPs, MVFs, MMFs via the Lean/Agile Requirements Dinosaur

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Comment: We’re reposting here a classic article from the archives of Yuval’s personal blog

What do Agile backlog items have to do with Dinosaurs?

I’ve been using a visualization that people find useful for understanding the relationship between the various Lean/Agile requirement containers. Some people call the full model a dinosaur. Others are reminded of the snake who ate an elephant from “The Little Prince”. (I’m sure there is a good connection to elephant carpaccio somewhere in here …)

Identifying a Unique Value Proposition

IMG_0449

 

The first step is to understand that for a new product there is a unique value proposition hypothesis. This is the area where your product/service will be unique.

The Minimum Viable Product (MVP)
IMG_0450

The next step is creating a Minimum Viable Product (MVP) to test your hypothesis. This is focused on your unique value proposition but typically also provides a little bit of “Table stakes” features just to make sure it is “Viable” as a product.

Evaluating your MVP Hypothesis

IMG_0451

Your MVP is also a hypothesis. It might be good enough to find Product-Market Fit or not. The case where each potential customer you engage tells you “This is great but in order for me to use it I need X” and X is different for each customer/user is shown below. This shows you are not in a Product Market Fit yet.

Pivot?

IMG_0452

If on the other hand, you are seeing more and more answers pointing to the SAME X then it makes sense to revise your Customer/Problem/Solution Hypothesis.

IMG_0453

You essentially are executing a Pivot. You are building MVP2 focused on the new hypothesis based on recent Customer Development learning generated by the previous MVP.

IMG_0454

Growth Stage

Let’s say MVP2 is successful and you are seeing real traction of early adopters. You want to increase growth and are looking for deeper penetration of your early adopters as well as bringing on new clients some of them beyond the early adopter’s crowd. Based on feedback you’ve been collecting and your product management research you have a couple of areas that can potentially bring this growth. Some of them, by the way, extend your unique value proposition and some of them make your current product more robust.

Steady Growth with Minimally Marketable Features

IMG_0455

In the case of areas with a strong indication of value, you might go straight for Minimally Marketable Features (MMF). Finding the minimum piece that can start bringing in growth. The aim of the MMF is to bring in value. It assumes high certainty that there is value in this area and that we know what the product needs to be to provide this value. The reason to break a big feature into smaller MMFs is mainly time to market and the ability to bring in value in many areas, always keeping your option to move to another area and provide value in it rather than focusing for too long on a single direction. An indication that you are working on MMFs is that when one is being shipped you feel comfortable working on the next MMF in that area. If on the other hand, you want to wait and see if your first MMF sticks…

Experiment using MVFs

IMG_0456

…then you are back in hypothesis land. But now your hypothesis is centered on a feature rather than your product. You have an area with high potential but also high uncertainty. The way to deal with it is to build a “pioneering” feature – the Minimum Viable Feature. The minimum feature that can still be viable for real use and learning from real customers.

IMG_0457

If you learn that the MVF has hit gold you can develop more MMFs in that area to take advantage (if that makes sense). If not, you can pivot to another approach towards that feature area, or at some point look for an alternative growth path. Essentially the MVF is a mini-me version of the MVP.

Voila – The Requirements Dinosaur!

IMG_0458

There you have it. The full model. Essentially my point is that you grow a product in uncertain markets by attempting various MVPs. Then once you achieve Product-Market Fit you mix MMFs and MVFs depending on the level of Business/Requirements uncertainty in the areas you are focusing on.

While MVPs/MMFs/MVPs are atomic from a business perspective (you cannot deploy and learn from something smaller) they might be quite big from an implementation perspective.

The dinosaur carpaccio now comes in as slicing each of those pieces here into smaller slices aimed at reducing execution/technology risk. (typically these are called User Stories) Those smaller slices might have tangible business value but on the other hand, some might not. It is more important for them to provide early implementation decision feedback along the way.

Feel free to use this model. Let me know what you think about it and how I can improve it!

Subscribe for Email Updates:

Categories:

Tags:

Value Streams
Agile for Embedded Systems
The Kanban Method
Agile Games and Exercises
Professional Scrum Master
Sprint Planning
LPM
Achieve Business Agility
Continuous Delivery
AI
Pomodoro Technique
Scrum.org
AI Artificial Intelligence
Manage Budget Creation
ATDD
Limiting Work in Progress
Program Increment
ARTs
Implementation of Lean and Agile
Continuous Improvement
TDD
Iterative Incremental Development
Atlassian
speed @ scale
User stories
Nexus and SAFe
Agile Games
SAFe
System Integration Environments
Lean and Agile Principles and Practices
Scrum Values
Scaled Agile Framework
Risk Management on Agile Projects
Agile Product Ownership
Process Improvement
Lean Budgeting
Agile Mindset
Agile
Entrepreneurial Operating System®
AgileSparks
speed at scale
Operational Value Stream
Covid19
Coaching Agile Teams
Kanban Basics
Agile Project Management
Agile Product Development
Scrum With Kanban
Scrum Master
agileisrael
Lean Agile
RTE Role
ATDD vs. BDD
Agile Project
Lean Software Development
Agile Assembly Architecture
NIT
Nexus
Nexus Integration Team
Lean Agile Leadership
ROI
SPC
Introduction to Test Driven Development
RSA
Sprint Retrospectives
Engineering Practices
Agile Israel Events
Rapid RTC
Agile Basics
Amdocs
An Appreciative Retrospective
Risk-aware Product Development
Agile Development
Spotify
Product Management
Lean Agile Organization
Built-In Quality
Perfection Game
Kaizen
Webinar
Applying Agile Methodology
Risk Management in Kanban
Kanban Kickstart Example
Lean Agile Management
Agile Marketing
Agility
Certification
Lean Risk Management
Elastic Leadership
Development Value Streams
Jira Plans
Portfolio for Jira
Software Development
Implementing SAFe
Release Train Engineer
PI Objectives
Releases Using Lean
Large Scale Scrum
Scrum Primer
Business Agility
Continuous Integration
QA
LAB
Slides
Agile Outsourcing
chatgpt
Tips
System Team
The Agile Coach
Continuous Planning
Nexus and Kanban
LeSS
Nexus vs SAFe
Planning
Scrum Master Role
Team Flow
Keith Sawyer
Managing Projects
Kanban
Legacy Code
Agile in the Enterprise
Change Management
A Kanban System for Software Engineering
Hybrid Work
Jira admin
Professional Scrum Product Owner
Agile Release Management
Agile Techniques
Test Driven Development
Sprint Iteration
Jira Cloud
Certified SAFe
Code
Jira
Games and Exercises
Frameworks
RTE
Scrum Guide
Kaizen Workshop
Agile India
Systems Thinking
Agile Testing Practices
Quality Assurance
POPM
IT Operations
SA
Lean Agile Basics
Tools
Kanban 101
Software Development Estimation
Artificial Intelligence
Principles of Lean-Agile Leadership
Video
Agile Release Planning
Agile Delivery
Scrum and XP
Lean and Agile Techniques
Professional Scrum with Kanban
Continuous Deployment
DevOps
EOS®
ALM Tools
Presentation
Agile Israel
Atlaassian
Legacy Enterprise
Lean-Agile Software Development
lean agile change management
Agile Contracts Best Practices
Product Ownership
Managing Risk on Agile Projects
SAFe Release Planning
predictability
ART Success
Enterprise DevOps
Daily Scrum
Self-organization
System Archetypes
Agile Community
Introduction to ATDD
Kanban Game
Reading List
Agile and DevOps Journey
Agile Program
GanttBan
Advanced Roadmaps
Lean-Agile Budgeting
Story Slicing
Acceptance Test-Driven Development
Agile Exercises
Lean Startup
BDD
What Is Kanban
WIP
PI Planning
Effective Agile Retrospectives
Agile Risk Management
Scrum
SAFe DevOps
Accelerate Value Delivery At Scale
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart