$$home_comment$$
A method based on grouping requirements into different priority groups with each group representing something stakeholders can relate to. For example, requirements can be grouped into critical priority, moderate priority and optional priority. Stakeholders may also classify requirements as compulsory, very important, rather important, not important, and does not matter in order to describe their importance.
The percentage of requirements that can be placed in each group can be restricted.
A prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.
The term Moscow itself is an acronym derived from the first letter of each of four prioritization categories: M - Must have S - Should have C - Could have W - Won't have
Participants are given randomly selected pairs of items and must evaluate the relative importance. This technique is particularly useful when there are many items and stakeholders (in the order of several hundreds).
Voting results can be convienently visualized and exported from the corresponding dashboard.
