We, as an industry, do ourselves a disservice by claiming that a product is ‘MVP’, short for “Minimum Viable Product”. Instead of labelling them a “Proof of Concept” or “Experiment”, many such projects fail at the tests of being “Viable” or “Product”. Let’s be more humane to our peers and customers by labelling “Experiments” as such, and ensuring that Products are minimally Production-ready.
While continuously iterating on a product is absolutely important to ensure that you’re working on products that people want, calling them “MVP” does not give an excuse for not making them Operable. There are terms for projects that are not Viable Products; Let us encourage the use of “Experiments” or “Proof of Concept” for such things that we want to run, but are unwilling to apply Production-ready rigor to, so as to set more reasonable expectations of support levels.
In this talk, I will discuss the points that make a Product “Minimally Viable”, such as:
Waldo is a Geek, Problem Solver, Systems/Operations Engineer, and DevOps Enthusiast. He tries to use his Viking Privilege superpowers for good, but is a flawed human being. He aspires to be a better bio writer one day.