7 ms·
The way I've understood it: Prototyping maybe be an effort to develop Requirements. It should not be used to develop a Product.
by ssmoot 11y ago
The way I've understood it: Prototyping maybe be an effort to develop Requirements. It should not be used to develop a Product.
- amelius 11y agoHow can I explain this to my boss? :)
- dakotasmith 11y agoInstead of explaining it, there can be steps taken to ensure a transition between prototype and product, such as prototyping in a language or for a stack that your company does not use in production.
- willismichael 11y agoAlternatively, if the company still forces you to push the prototype to production, this can be a great way of sneaking in the technology stack that you wanted to use in the first place.
- MichaelGG 11y agoMake it look like a prototype? I've taken to plastering big warning on non-production systems. Otherwise someone looks at a fragile dev environment, doesn't see it breaking outright, then goes and sells live customers into it and uses the prototype/demo system to setup real accounts. No amount of verbal or email warnings will change this. Hurray, now the one-off demo system is a production environment! As a bonus, you get to write data migration programs to move these customers to the entirely-unrelated final product! But instead, if there are big red Xs and so on in the UI, then it becomes clear "oh this is a prototype/demo/".
- HenryTheHorse 11y ago> It should not be used to develop a Product. I disagree with that conclusion. Prototypes help in both clarifying requirements as well as eliciting requirements. However, for the latter, a prototype may be necessary but not sufficient.