What is Moscow prioritization? Definition, procedures and frequently asked questions (2023)

What is Moscow prioritization?


MoSCoW Prioritization Definition

MoSCoW prioritization is a tool to create a hierarchy of priorities during a project. It is based on the agile method of project management, which aims to strictly establish factors such as cost, quality, and requirements of a product as soon as possible. "Moscow" is an acronym for must have, should have, could have, and will not have, each denoting a category of prioritization.

MoSCoW is an acronym that defines four prioritization categories:I have to-to have,Should-to have,could-have andhabit-to have. The o's are only included to help with pronunciation.

MoSCoW prioritization solves one of the main problems of less robustpriorizationTools by establishing specific definitions for each priority level.

For example, if something is at the "must have" level of MoSCoW, everyone on the team knows right away that this feature cannot be overlooked during project development.

In this guide, we'll look at how product teams can prioritize the use of the MoSCoW framework, how to perform a MoSCoW analysis, and how to write MoSCoW requirements. let's go in

Origins of the MoSCoW framework

In 1994, Dai Clegg was a software development consultant at Oracle. The teams used RAD (Rapid Application Development) but had limited time, which led Dai Clegg to create the MoSCoW rule to prioritize development tasks during product launch.

The MoSCoW rule became popular in the context of agile project execution.DSDM(Dynamic Systems Development Method) in the early 2000s. DSDM attempts to improve RAD development.

A strategy is necessary to determine the cost, quality and time requirements at the beginning of the project. Moscow fits the picture.

Asagilehas gained popularity, the value of the Moscow Rules in decision-making has become clear. MoSCoW is now a widespread method for prioritization within the agile framework.

What is Moscow prioritization? Definition, procedures and frequently asked questions (1)

Get our domain prioritization ebook

Learn to prioritize by making it a simple process to create products that stand out. Learn more about how to discover information, choose the right prioritization framework, and more.

Get the ebook

(Video) What is MoSCoW Prioritization Method? Definition, Overview, and Best Practices

How does MoSCoW work in the agile area?

The MoSCoW method plays an important role here.agile development. The technology is based on the agile project management model.

The focused and iterative nature of Agile development forces teams to ruthlessly refineRequirementto what is needed for a particular iteration. Moscow fits well into this process.

for example aMinimum Viable Product (MVP)consists only of requirements that are "must have".

In agile development, the requirements must be re-evaluated after each iteration and with new versions.user storiesdevelop.

not asDSDM, agile development's focus on changing user requirements, and constant course fixes make the Moscow Rule a regular exercise rather than a one-time task to be accomplished and set in stone.

Each of the project's agile elements can be prioritized into Musts, Shoulds, Coulds, and Shouldn'ts, so teams can implement solutions quickly, use resources efficiently, and integrate those new or changing requirements.

In an agile development environment, the MoSCoW definition of "shall not" can be seen as "shall not have for now", recognizing that current iterations will focus on a subset of requirements and future iterations will contain more features.

MoSCoW also helps when agile development forces teams to focus on higher priorities by limiting time and resources with tools likehustleor timeboxing, forcing activities into a fixed time frame.

Other agile techniques that involve users in the design process are limited by the time users can afford to help with development. MoSCoW can help prioritize users' time and effort for the most important features.

(Video) How to prioritise using MOSCOW prioritisation - Agile Project Management

How to make a prioritization of Moscow?

Now that you know a bit more about what Moscow prioritization is, let's see how to put it into practice: What are the rules for Moscow prioritization and how to perform Moscow analysis? Here are the stepsand best practicesfor carrying out its own prioritization of Moscow.

Download now: Get our 5-minute guide to using the MoSCoW prioritization technique

First, let's start writing the MoSCoW requirements.

1. Determine your project requirements

Although MoSCoW prioritization should be used early in the project management cycle, it should not be your first step. You must have project requirements in place before you can organize those requirements by priority. So the sooner your team can establish those priorities, the better.

Like all steps of MoSCoW prioritization, this step should be done jointly by bothproduct teamyInterested people.

2. Define your prioritization levels

As mentioned, theThe Moscow model consists of four components.: essential, essential, possible and unwanted. Although the title of each category makes its purpose quite clear, it is important that each level is clearly defined.

So how do you write each of these MoSCoW requirements and decide which tasks belong to which level?

I need to have

These product characteristics should be the easiest to determine. If you were designing a car, these would be the tires, engine, and fuel. When creating a quote service, the ability to integrate with a user's bank account can be a must-have component.

In other words, these are them.MinimumThe requirements of your project: they are not negotiable. If you're having trouble determining which features to put in this category, just ask yourself, "If this feature/milestone/component is not met, will the project fail?" If the answer is yes, then this is an indispensable component.

Should have

Your project must-haves are those features that are not essential to the success of the project, but still add significant value. These characteristics are more oriented to satisfy the desires and expectations of customers than to satisfy their basic needs.

Going back to our car example, one component to have would be air conditioning. This is not necessary for the car to run, but a car without air conditioning would be a hard sell. Like the must-haves, you want to try to hit all the must-have milestones by the end of the project.

Could have

This is the general category for features that are neat, interesting, or fun, but don't necessarily serve a larger purpose. These are the comfort elements, the bonuses, of your product. You may find that this is the area where the most changes occur during the project, with features moving from this category to the have-nots and should-haves.

(Video) MoSCoW prioritization for your product backlog ✅

To determine if a feature is a beauty or a must, consider how it affects your product's value to customers. In most parts of the world it will be almost impossible to sell a car without air conditioning as a "good" car. A car without a parking camera, while a useful feature, is unlikely to drastically decrease the perceived value of the car. So in this category, you put features that sweeten the deal but don't affect or detract from the success of your product.

I do not have

Finally, we have the I don't want to have. This category is likely to fill with ideas as you progress through the project development cycle. Essentially, this is where you add features that you want to include in your product but for some reason can't.

Or you don't have the technology, talent, resources, or confidence to try to implement a specific component in your product. Instead of throwing that idea away in a notebook and forgetting about it, put it here for future reference. You may find that some of your opportunities, and perhaps even some opportunities that you should have, don't really exist due to unexpected constraints.

3. Organize your needs into priority levels

Once you've established your requirements and clearly defined your priority levels, it's time to categorize your requirements into priority levels.

"Must have" requirements should be easy to identify, as these are the things without which your project cannot function. However, for the other levels, it may be useful to consider a few other factors when determining which requirements fall under which category:

  • time restrictions

  • teamwork

  • budget constraints

  • team workload

  • Collaboration between teams

Not only should features and ideas be placed at each level of the MoSCoW model, but a clear amount of resources allocated for each level should also be agreed upon.

4. Refine and optimize

At this point, your team should be done with the initial phase of categorizing all project requirements by priority. However, this does not mark the end of the Moscow process. Each time a milestone is completed, the remaining milestones must (briefly) be reassessed.

For example, you may have requirement X that falls into the "could have been" category during your first MoSCoW meeting. However, once you complete a few must-haves, you may see requirement X differently and decide that you need to implement it more urgently or that it adds no value at all.

A flex element is good during development, though you shouldn't change your MoSCoW model so drastically that it becomes unusable. The secret is finding a sweet spot between iterative evaluation and a structured way of working.

(Video) PRINCE2® - The MoSCoW Prioritisation Technique

What is Moscow prioritization? Definition, procedures and frequently asked questions (2)

Get our domain prioritization ebook

Learn to prioritize by making it a simple process to create products that stand out. Learn more about how to discover information, choose the right prioritization framework, and more.

Get the ebook

Why the prioritization of Moscow matters

There are several reasons why the MoSCoW method is useful for making a solid product. First, it helps you create a timeline for your project by determining what needs to be completed first. Everyone knows the most important features that give clarity to the entire project.

Second, the MoSCoW approach is great for setting expectations for the project, both for the team and for theinterested people. It gives investors a good idea of ​​what to expect from the project, as well as a clear idea of ​​what each feature will cost.

Third, implementing MoSCoW into your workflow helps keep the project vision on track. When you brainstorm with colleagues, encourage their creativity, and try to go above and beyond, it's only natural for your team to go beyond project requirements and boundaries.

While that's good for the drawing board, it's not so great when you're actively developing the product. Moscow offers everyone a clear list of what they must achieve. against a vague and multifaceted vision.

What is Moscow prioritization? Definition, procedures and frequently asked questions (3)

What is Moscow prioritization? Definition, procedures and frequently asked questions (4)


What is MoSCoW prioritization? ›

MoSCoW prioritization, also known as the MoSCoW method or MoSCoW analysis, is a popular prioritization technique for managing requirements. The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won't-have, or will not have right now.

What is the MoSCoW method of importance? ›

The MoSCoW method is 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; it is also known as MoSCoW prioritization or MoSCoW analysis.

What does MoSCoW mean in project management? ›

MoSCoW (Must Have, Should Have, Could Have, Won't Have this time) is primarily used to prioritise requirements, although the practice is also useful in many other areas.

What is the meaning of MoSCoW? ›

Meaning of Moscow in English

Moscow. /ˈmɒs.kəʊ/ us. /ˈmɑː.skoʊ, ˈmɑː.skaʊ/ the capital city of Russia, situated in the west of the country. Towns & regions: city names & their inhabitants.

How to do MoSCoW analysis? ›

The MoSCoW abbreviation (except for the o's) is carved with first letters of the priority categories it works with. These are Must-haves, Should-haves, Could-haves and Won't-haves. And that's how you can define which task falls into which category.

What are 3 facts about MoSCoW? ›

11 Interesting Moscow Facts You Should Know
  • Lenin's corpse is preserved in a Mausoleum in Moscow's Red Square.
  • Moscow's stray dogs can navigate the metro.
  • Yuri Gagarin, the first man in space, is buried at the Kremlin Wall in Moscow.
  • Only 2 percent of Moscow's population are 'from' Moscow.

What are prioritization techniques? ›

Prioritization techniques for agile are tools that help you prioritize a list of tasks or actions in very different manners. The idea behind these techniques is to increase your productivity by helping you define and manage priorities.

What are the three prioritization methods? ›

They've built great things, and built even greater prioritization frameworks! Here, we'll show you the top three methods that all Product Managers should know; MoSCow, RICE, and Kano.
  • The MoSCoW Method. ...
  • RICE Scoring. ...
  • Kano Model.

Why is it called a MoSCoW? ›

The city was named after the Moskva river, on which the city is situated. Finno-Ugric tribes used to live on the territory of the present-day Moscow. The name of the Moskva river most probably originates from an ancient Finnic language.

Why was Moscow created? ›

Moscow grew from the personal ambitions of its rulers, ambitions that were given an immediacy and perceived necessity by the challenges that those ambitions faced. Kieven Rus, a few years before Moscow was founded. Moscow's future site, on a relatively minor river, has been added with a red arrow.

What is the symbol of Moscow? ›

The coat of arms of Moscow depicts a horseman with a spear in his hand slaying a basilisk and is identified with Saint George and the Dragon. The heraldic emblem of Moscow has been an integral part of the coat of arms of Russia since the 16th century.

What is Moscow in agile? ›

It's based on the agile method of project management, which aims to strictly establish factors like the cost of a product, quality, and requirements as early as possible. “MoSCoW” is an acronym for must-have, should-have, could-have, and won't-have, each denoting a category of prioritization.

What are three main characteristics of a priority matrix? ›

In this simple priority matrix there are:
  • Three levels of Urgency (High/Mid/Low)
  • Three levels of Impact (High/Mid/Low)
  • Five levels of Priority (1 to 5, with 1 as the highest priority)

What is MoSCoW requirements template? ›

What is the MoSCoW prioritization exercise? Use the MoSCoW template to prioritize items, like features, by classifying them as Must, Should, Could, and Won't. This simple prioritization method quickly aligns individuals & teams, and prompts discussions where there are different points of view.

What did Moscow used to be called? ›

The area was first named "Hog Heaven" which was later changed to "Paradise Valley." In 1877, Samuel Neff filed for a postal permit under the name of Moscow because the area reminded him of his hometown of Moscow, Pennsylvania. In 1875, the city's first store was opened on what is now Main Street.

When was Moscow founded and why? ›

Moscow was founded in 1147. It is one of the oldest cities in Russia. The year of the city foundation is generally accepted to be 1147 when prince Yuri Dolgorukiy called upon his brother, the prince of the Novgorod-Severski to "come to me, brother, to Moscow." This is the first record of Moscow in Russian chronicles.

What is the brief history of Moscow? ›

Moscow traces its history back to 1147, when it was mentioned in the chronicles for the first time. The early 12th century saw Kievan Rus disintegrate into many separate principalities. During this period, Prince Yury Dolgoruky of Rostov and Suzdal (1090–1157) began to build new towns and communities.

What are the 4 P's of prioritization? ›

The 4 P's: prioritizing, pacing, planning, and positioning - provide four different paths to help you effectively manage and navigate persistent pain in your everyday life.

What is the ABC of prioritization? ›

The ABC Method was originally developed by Alan Lakein and consists of assigning a priority status of “A,” “B,” or “C” to each of the items of your to-do list or task list. High priority, very important, critical items, with close deadlines or high level importance to them.

How many methods of prioritization are there? ›

Prioritization methods base these important decisions on objective, relevant criteria instead of subjective opinions. This article outlines 5 methods for prioritizing work into a UX roadmap: Impact–effort matrix. Feasibility, desirability, and viability scorecard.

What are the examples of prioritization? ›

An example of this could be: “I'd be lost without my daily to-do list! At the beginning of each workday, I write out tasks to complete, and list them from highest to lowest priority. This helps with my workflow and keeps me on track with what needs to get done for the day.”

Why is Moscow a circle? ›

It is common knowledge that Moscow was built on seven hills and has several inner rings. At first, there were ramparts that marked the limits of the early settlement. Over time, new belts emerged. These were mostly roads that encircled the steadily expanding city.

Is there a Moscow in the US? ›

Moscow (/ˈmɒskoʊ/ MOS-koh) is a city in North Central Idaho, United States. Located along the state border with Washington, it had a population of 25,435 at the 2020 census.

How big is Moscow? ›

What is MoSCoW political system? ›

The 1993 constitution declares Russia a democratic, federative, law-based state with a republican form of government. State power is divided among the legislative, executive, and judicial branches.

How is MoSCoW governed? ›

The Government of Moscow is headed by the highest official of the city of Moscow, i.e. the Mayor of Moscow. The members of the Government of Moscow are the Mayor of Moscow, the Deputy Mayors of Moscow in the Moscow Government and the Moscow Government ministers.

What is the difference between Russia and MoSCoW? ›

Moscow is the capital city and the most populous federal subject of Russia. The city is a major political, economic, cultural and scientific center in Russia and in Eastern Europe.

Why is it called a Moscow? ›

The city was named after the Moskva river, on which the city is situated. Finno-Ugric tribes used to live on the territory of the present-day Moscow. The name of the Moskva river most probably originates from an ancient Finnic language.

What type of economy is Moscow? ›

Russia has a market-based economy with a high level of state involvement, and many government officials are quite wealthy. The Russian currency is the ruble. One ruble is worth approximately $0.016 U.S. dollar. 2.

Who does Moscow belong to? ›

Moscow, Russian Moskva, city, capital of Russia, located in the far western part of the country.

Who controls Moscow Times? ›

The Moscow Times
TypeOnline newspaper, formerly also print
Owner(s)Tiamti PLC (Russian: ООО Тиэмти) supported by Dutch foundation Stichting 2 Oktober
PublisherDerk Sauer
Editor-in-chiefSvetlana Korshunova
Cultural editorMichele A. Berdy
9 more rows

How is Moscow divided? ›

Administratively, the city is divided into 12 administrative okrugs, which in turn are subdivided into 146 administrative units. Municipally, each of the 146 administrative units have municipal status as 125 municipal districts and 21 municipal settlements.

What federal subject is Moscow in? ›

In 1993, the Russian Federation comprised 89 federal subjects.
Federal subjects of Russia.
Federal subjects Субъекты федерации (Russian)
Created12 December 1993
Populations41,431 (Nenets Autonomous Okrug) – 13,010,112 (Moscow)
Areas864 km2 (334 sq mi) (Sevastopol) – 3,103,200 km2 (1,198,200 sq mi) (Sakha Republic)
5 more rows

What do they call Moscow? ›

It is probably obvious why Moscow is often called the First Throne. Moscow was the first city which became the center of all united Russian lands and later the capital of all Russia.


1. MoSCoW Prioritization | What it is and how to do it
2. Agile in Practice: Prioritisation using MoSCoW
3. [Top 80] Business Analyst Interview Questions and Answers
4. Mastering MoSCow Prioritization
5. MoSCoW prioritization
(Project Management)
6. Business Analyst Training For Beginners | Requirement Prioritization Techniques
Top Articles
Latest Posts
Article information

Author: Moshe Kshlerin

Last Updated: 18/06/2023

Views: 5704

Rating: 4.7 / 5 (77 voted)

Reviews: 84% of readers found this page helpful

Author information

Name: Moshe Kshlerin

Birthday: 1994-01-25

Address: Suite 609 315 Lupita Unions, Ronnieburgh, MI 62697

Phone: +2424755286529

Job: District Education Designer

Hobby: Yoga, Gunsmithing, Singing, 3D printing, Nordic skating, Soapmaking, Juggling

Introduction: My name is Moshe Kshlerin, I am a gleaming, attractive, outstanding, pleasant, delightful, outstanding, famous person who loves writing and wants to share my knowledge and understanding with you.