The second concept that software teams take pride in is the Minimum Viable Product (mvp), which seeks to answer the question: what is the cheapest and fastest product that we can build to help us to learn something of value? My observation of software teams is that we use mvp as a scope management paradigm. When we have to do many things in the backlog and time/budgets are limited, we identify the mvp. Once again, the intent of releasing a usable product under given constraints is commendable, but an mvp defined based on the two dimensions of time and budget isn't really an mvp.
In early 2016, coach and consultant Henrik Kniberg came up with this drawing (https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp). It has caught on quite well and is popular among Agile practitioners. As Henrik writes in his blog, "The picture is a metaphor. It is not about actual car development, it is about product development in general, using a car as a metaphor."
The...