What is the Moscow method?
The MoSCoW method (or MoSCoW prioritization) is a process by which product managers manage product requirements. There are four categories for labeling the MoSCoW requirements: must-have (M), should-have (S), could-have (C), and won't-have (W).
What are the MoSCoW method prioritization categories?
While product teams have many methods for prioritizing their product features or initiatives, the Moscow method prioritization uses four categories to distinguish importance.
- Must-have: These are non-negotiable items in the list that are necessary for the project, product, service, or software update. These features are usually essential to making the product work or render the product useless if they're not implemented.
- Should-have: These are items that provide good value for the company or the customer, but the product will still work without them.
- Could-have: These non-essential functions still provide value to the company or consumer, but they're less essential than "should-have" items. These items are usually deprioritized or pushed to future releases in product development.
- Won't-have: Just like it sounds, the team agreed these items aren't necessary for the release, update, or launch.
How to use the Moscow method technique
- Setting the stage: Your product team and stakeholders need to align on factors for prioritizing new items. Often, teams will use factors like budget, resources, expertise, and company needs to determine priority.
- Creating the list: Your product team and stakeholders should also align on a list of initiatives, features, or items that need to be prioritized.
- Using the Moscow method to categorize features: After a list has been created, the team will use the Moscow method to categorize each item as a must-have, should-have, could-have, or won't-have using the factors agreed upon during the first step.
- Leveraging the results: Now, your team has a clear list of priorities. This list can be used as a product backlog for an initiative and highlight which items to focus on as you march toward a release date.
Examples of the Moscow Framework
Example 1: A mobile app development project using the Moscow method
A team was tasked with developing a new mobile app for a retail company. The team used the Moscow Method to prioritize the features they wanted to include in the app. They identified that a barcode scanner, inventory lookup, and loyalty program integration were must-have features for the app. These features were deemed necessary for the app to be functional and meet the needs of the company and its customers. The team also identified that a wishlist feature, personalized recommendations, and push notifications were should-have features. These features would provide value to the company and customers, but the app would still work without them. Finally, the team decided that a virtual try-on feature, augmented reality, and social sharing were could-have features. These features were considered non-essential and were deprioritized or pushed to future releases. Using the Moscow Method, the team was able to focus on the most important features and deliver a functional and valuable app to the company and its customers.
Example 2: A software update for a SaaS company
A SaaS company was working on an update for its platform. The company's product team used the Moscow Method to prioritize the features they wanted to include in the update. They identified that improved security and compliance features were must-haves for the update. These features were deemed necessary for the platform to meet industry standards and protect the data of the company's customers. The team also identified that improved scalability, enhanced analytics, and automation features were should-have features. These features would provide value to the company and its customers, but the platform would still work without them. Finally, the team decided that support for multiple languages, custom branding, and additional integrations were could-have features. These features were considered non-essential and were deprioritized or pushed to future releases. Using the Moscow Method, the team was able to focus on the most important features and deliver a functional and valuable update to the company's customers.
The Moscow Method and Kano Model are two popular techniques used in product development to prioritize features and initiatives. Both methods have their own strengths and weaknesses, and it's important to understand the differences between them to determine which one is best suited for your project.
Comparing the Moscow Method and Kano Model
The Moscow Method categorizes requirements into four groups: must-have, should-have, could-have, and won't-have. This method is effective for identifying the most important features and ensuring that they are included in the final product. However, it can be difficult to determine the difference between should-have and could-have features, leading to confusion and potential misprioritization.
On the other hand, the Kano Model focuses on customer satisfaction by identifying three types of features: basic, performance, and excitement. Basic features are necessary for the product to function, performance features provide incremental improvements, and excitement features drive customer loyalty. The Kano Model helps teams understand the relationship between customer needs and the features of the product. However, it can be time-consuming to gather customer feedback and may not provide a clear prioritization of features.
When it comes to choosing a prioritization model for your product development team, it can be tough to decide between the Moscow Method and the Kano Model. Both have their own strengths and can get the job done when used correctly. But, it really comes down to what your specific project needs and what your team's goals are. Take a look at the unique characteristics of your project and see what method aligns best with your team's preferences before making a final decision.
Get Started for Free or Schedule a Live Demo to Learn More
