The Moscow method is a prioritization technique used across various domains to understand how work needs to be prioritized for completion. This popular acronym represents four categories of priority for the product/team:  Must have - requirements that are critical or non-negotiable and mandatory  Should have - requirements that are not vital, but are important and add significant value  Could have - requirements that are nice to have and have the least impact if not done  Won't have - requirements that are not a priority and can be done to add some/little value if time permits (also known as Would have or wish to have requirements)  Moscow aims at creating a hierarchy of requirements based on factors that define priority such as:  The business value of the delivery  Release priority  Effort complexity  Budget constraints  Team skill set  Organizational priorities/goals  Cost-benefit analysis  Product ranking  Stakeholder inputs  These along with other factors that may be specific to the organizational processes help in determining which requirements fit into the MoSCoW prioritization to be picked up for the roadmap planning exercise (or development or testing).