Most of us know what an MVP is supposed to do. .. in theory. An MVP is an early product version that is simple, cheap, and quick to build, so you can test it with real users. But if it's so simple, why do some engineering teams get stuck iterating on MVP-quality code? Why is it so hard to throw the MVP away and start from scratch? In this week's discussion, Stephan and I try to clarify this conundrum with some concrete examples.