User:Rdicerb (WMF)/sandbox
Defining "Minimum Viable Product" for Wikimedia-hosted communities[edit]
Within product development there lives the concept of Minimum Viable Product (MVP), used in building and iterating web products and features.
My MVP perspective from a community-minded space, regardless of what the product is intended to do (may not include perspective of all PMs, engineers, designers, community members):
- Code must be secure/ no security holes, etc
- If it is a product that adds to the user experience, it can be iterated in production. If it is a product which replaces an existing functionality, it cannot break/remove workflows without user consultation (primarily, those who utilize that workflow) or known request for removal.
- Could also argue for "it needs to completely replace all workflows already available in the replaced product, unless deemed unneeded by users."
- Is there anything that can be left out and put into the roadmap for post-production (community ask).
Re: iteration[edit]
Much like Wikipedia articles are iterative, so is software development. Sometimes features will be built that need to be tweaked or needs to evolve to be more useful.