Dear all,
“Half the money I spend on implementing requirements is wasted; the trouble is I don’t know upfront which half.” This adaption of John Wannamaker’s famous quote probably describes the situation of many corporate IT teams fittingly. Users (and humans as such) are simply not wired to know and describe their needs and wants in detail until they see some implementation of them.
Building and testing MVPs or prototypes to find out before implementing is a lot easier than most of us think. Here are three reads that – even as they are written for startups – explain the concept of MVPs and some of the most effective ways of creating them for every stage of a project.
| What Type of MVP is Right for Your Startup?
is a very readable introduction to the concept of MVPs, the most popular MVP types and which type to use at which project stage. |
18 Types of Minimum Viable Product (MVP) That Won’t Break the Bank is exactly what the title says. The article also describes when to use LowFi and HiFi MVPs.Click to read! |
Pretotype and forget about prototyping and MVP’s Gijs Mensing takes a slightly contrarian view and introduces “digitalised paper apps” to collect feedback. Effective!Click to read! |
Beyond the POP-app mentioned in Gijs Mensing’s post, Keynotopia is another easy-to-use prototyping resource for everyone who knows how to use PowerPoint.
Have fun creating your first MVP,
Godehard