MoSCoW method - Wikipedia

Would is used to indicate features that are not required now, but should be considered in architectural terms during the design as future expansion opportunities - this avoids the risk of dead-end designs that would inhibit a particular feature being offered in the future. In new product development, particularly those following agile software development approaches, there is always more to do than there is time or funding to permit (hence the need for prioritization). For example, should a team have too many potential epics (i.e., high-level stories) for the next release of their product, they could use the MoSCoW method to select which epics are Must have, which Should have, and so on; the minimum viable product (or MVP) would be all those epics marked as Must have.