So your product discovery has gone well. Following the identification and validation of your solution, it's time to build your Minimum Viable Product (MVP).
It should have just enough functionality to test the risks you've identified, but also be engaging. In addition, it should enable you to measure and adapt. The MVP is not a product but a process in this sense.
“Your first product is a tool to learn what product to build” Alistair Croll, Lean Analytics
The purpose of this blog post is to describe how low-code applications can assist with this process. I illustrate my arguments by building a small MVP example application. I conclude by comparing low-code and code approaches.
The full article can be found here:
