Minimum Awesome Product An Article by Carlos Beneyto theuxblog.com Show image 0 Show image 1 Users are accustomed to a minimum of quality, and they expect that of all new products. If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect. Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born. Understanding the Kano ModelDon't Serve Burnt PizzaWhat happens to user experience in a minimum viable product? qualityuxfeaturessoftware
Complete and consistent requirements An architect who needs complete and consistent requirements to begin work, though perhaps a brilliant builder, is not an architect. Mark W. Maier & Eberhardt Rechtin, The Art of Systems Architecting What the problem isThe heart of systems engineeringA late change in requirements is a competitive advantage architecturedesign