{"id":108380,"date":"2026-01-25T06:49:40","date_gmt":"2026-01-25T11:49:40","guid":{"rendered":"https:\/\/monday.com\/blog\/?p=108380"},"modified":"2026-09-26T03:16:11","modified_gmt":"2026-09-26T08:16:11","slug":"moscow-prioritization-method","status":"publish","type":"post","link":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/","title":{"rendered":"What is the MoSCoW method? A guide to prioritizing what matters"},"content":{"rendered":"<div class=\"text-block\" id=\"text-block-1\">\n<p>Every team faces more requests than it can deliver in the time available. And when everything looks urgent, it can be tempting to promise to deliver all of it, even though you know there&#8217;s a strong risk you&#8217;ll miss the deadline. The MoSCoW method gives you a shared, honest way to decide what ships now and what waits.<\/p>\n<p>This guide breaks down the 4 MoSCoW categories, where the framework came from, and how to run it step by step. You&#8217;ll also see a worked prioritization matrix, the effort-balancing rules that keep releases realistic, and how to manage the whole process on monday AI Workspace.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"1\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-2\">\n<h2 class=\"h2 text-block__title\">Key takeaways<\/h2>\n<ul>\n<li>The MoSCoW method sorts work into 4 priority categories: must-have, should-have, could-have, and won&#8217;t-have (this time).<\/li>\n<li>It comes from the Agile DSDM framework and works best inside a fixed timebox or <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">release cycle<\/a>.<\/li>\n<li>The won&#8217;t-have category is the method&#8217;s key strength, because naming exclusions upfront prevents <a href=\"https:\/\/monday.com\/blog\/project-management\/keep-scope-creep-undermining-project\/\">scope creep<\/a>.<\/li>\n<li>DSDM recommends keeping must-have work to about 60% of effort and holding roughly 20% as could-have contingency.<\/li>\n<li>On monday AI Workspace, priority columns, dashboards, and AI agents keep every MoSCoW decision visible and current as work shifts.<\/li>\n<\/ul>\n\n<img width=\"1024\" height=\"595\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2019\/08\/dependency-and-risk-mapper--1024x595.png\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2019\/08\/dependency-and-risk-mapper--1024x595.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2019\/08\/dependency-and-risk-mapper--300x174.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2019\/08\/dependency-and-risk-mapper--768x447.png 768w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2019\/08\/dependency-and-risk-mapper-.png 1087w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-3\">\n<h2 class=\"h2 text-block__title\">What is the MoSCoW method?<\/h2>\n<p>MoSCoW prioritization is a tool for creating a hierarchy of priorities before and during a project. It stems from the <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-project-management\/\">Agile project management method<\/a>, which aims to establish elements like product cost, quality, and project requirements as early as possible.<\/p>\n<p>MoSCoW stands for must-have, should-have, could-have, and won&#8217;t-have (this time). Each item in the acronym denotes a category of prioritization. The idea is that items are sorted at the start of a project to clarify what is strictly necessary, what is desirable, and what the project can do without.<\/p>\n<p>You&#8217;ll also see the approach called the MoSCoW framework or the MoSCoW model, but the mechanics are the same in every version. It&#8217;s a fast, low-jargon way to turn a long list of competing demands into an agreed order of delivery that your whole team can read at a glance.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-4\">\n<h2 class=\"h2 text-block__title\">Where does the MoSCoW method come from?<\/h2>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/software-development-process\/\">Software developer<\/a> Dai Clegg created the MoSCoW method in 1994 for use in rapid application development (RAD). A <a href=\"https:\/\/arxiv.org\/abs\/2402.13149\">2024 requirements-prioritization survey<\/a> attributes its introduction to Clegg while he was at Oracle UK. He designed it to help teams agree on priorities quickly during <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">product releases<\/a>.<\/p>\n<p>The lowercase Os carry no meaning and exist only to make the acronym easier to pronounce. Practitioners then used it extensively within the Dynamic System Development Method (DSDM) from 2002 onward. The DSDM Consortium, now the Agile Business Consortium, adopted and documented the method, and it maintains the canonical definition today.<\/p>\n<p>Clegg built MoSCoW for fast, timeboxed cycles where time and resources are fixed and scope has to flex.\u00a0Understanding its origin helps you apply it where it performs best \u2014 release planning and sprint scoping.<\/p>\n\n<img width=\"1024\" height=\"563\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/AI-risk-identification-1-1-4.jpg\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/AI-risk-identification-1-1-4.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/AI-risk-identification-1-1-4-300x165.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/AI-risk-identification-1-1-4-768x422.jpg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-5\">\n<h2 class=\"h2 text-block__title\">What do the 4 MoSCoW categories mean?<\/h2>\n<p>The four MoSCoW categories are the heart of the method. Each one answers a single question: how badly does the project need this item to succeed? Here&#8217;s what each category means, using the standard definitions.<\/p>\n<ul>\n<li><strong>Must-have:<\/strong>\u00a0These items are essential for the <a href=\"https:\/\/monday.com\/blog\/project-management\/how-to-define-project-success\/\">success of the project<\/a>. There can be no compromise on whether they are included, because without them, the entire project would be meaningless. In short, this is a top-priority MoSCoW requirement.<\/li>\n<li><strong>Should-have<\/strong>:\u00a0These items are those that are important but not absolutely essential like those in the &#8220;must-have&#8221; category. Elements in this category are considered a secondary priority; that is, they are important, but not crucial to success.<\/li>\n<li><strong>Could-have<\/strong>: These items would be nice to have but are not essential. Still less important than the two preceding categories, these elements are considered a third-level priority. If including them will have negative consequences on cost or meeting deadlines, they should be omitted. It is only when they don&#8217;t negatively affect other project elements that they should be included.<\/li>\n<li><strong>Won&#8217;t-have (this time)<\/strong>: These items are those that are not essential and can be excluded from the project without jeopardizing its success. Being the lowest priority category, omitting them won&#8217;t hurt the project and they can be included when project conditions are more favorable. Note that most teams rush past won&#8217;t-have, but it does the heavy lifting. Naming what you won&#8217;t build this time, helps you make exclusions explicit and visible to stakeholders. That single act of writing it down is the strongest defense you have against scope creep later in the cycle.<\/li>\n<\/ul>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-6\">\n<h2 class=\"h2 text-block__title\">When should you use the MoSCoW method?<\/h2>\n<p>MoSCoW works best in specific situations where time is fixed and you need to make fast, shared decisions about what ships. Use it when:<\/p>\n<ul>\n<li><strong>You&#8217;re planning a timeboxed release or sprint:<\/strong> MoSCoW was built for fixed cycles where scope has to flex, so it&#8217;s ideal for Agile teams deciding what fits in the next iteration.<\/li>\n<li><strong>Stakeholders disagree on what&#8217;s urgent:<\/strong> When everyone thinks their request is critical, MoSCoW forces a shared conversation about what the project actually needs to succeed.<\/li>\n<li><strong>You&#8217;re facing more requests than capacity:<\/strong> If your backlog is longer than your timeline, MoSCoW helps you draw a clear line between what you&#8217;ll deliver now and what waits.<\/li>\n<li><strong>Scope creep is threatening the deadline:<\/strong> The won&#8217;t-have category makes exclusions explicit and visible, so new requests don&#8217;t quietly expand the plan mid-cycle.<\/li>\n<li><strong>You need a fast prioritization framework:<\/strong> MoSCoW doesn&#8217;t require scoring models or complex calculations, so you can sort a backlog in a single working session.<\/li>\n<li><strong>You&#8217;re kicking off a project and priorities are unclear:<\/strong> Use MoSCoW as a discussion tool to align your team on what matters most before work begins.<\/li>\n<\/ul>\n<p>But MoSCoW doesn&#8217;t handle everything. It doesn&#8217;t account for task dependencies, technical sequencing, or factors that might shift the order of delivery. Use it as one tool in a broader set of prioritization and task-management strategies, such as RICE or <a href=\"https:\/\/monday.com\/templates\/eisenhower-matrix\">Eisenhower<\/a>, not as a replacement for planning the how.<\/p>\n\n<img width=\"1024\" height=\"563\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/Project_management-47.jpg\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/Project_management-47.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/Project_management-47-300x165.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/09\/Project_management-47-768x422.jpg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-7\">\n<h2 class=\"h2 text-block__title\">MoSCoW method: the pros and cons<\/h2>\n<p>MoSCoW is widely used in Agile projects with fixed timeboxes because it helps teams manage release requirements quickly. It&#8217;s proven effective, but it&#8217;s not perfect. The table below breaks down where the method delivers value and where it falls short.<\/p>\n\n<table id=\"tablepress-3924\" class=\"tablepress tablepress-id-3924\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Pros<\/th><th class=\"column-2\">Cons<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Easy to master: The method uses simple principles that require little background research to understand and apply.<\/td><td class=\"column-2\">Priority requirements can be subjective: Categorization relies on judgment rather than numerical data, which can lead to conflicting opinions about what qualifies as a must-have.<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Helps prioritize: It creates a clear visual hierarchy of priorities, so teams always know which elements matter most.<\/td><td class=\"column-2\">Items require background context: Accurate categorization demands context for each item, which can be time-consuming and tedious to gather.<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Useful for team discussions: MoSCoW serves as a conversation starter that gets team members aligned and sharing ideas openly.<\/td><td class=\"column-2\">Doesn't account for change: Fixed categories don't adapt when circumstances shift mid-project, so an item that's not necessary at the start may become critical later.<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Helps achieve stakeholder consensus: When stakeholders participate in categorization, they gain a shared understanding of the project and agree on what takes priority.<\/td><td class=\"column-2\"><\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Can prevent scope creep: Setting clear, fixed priorities at the start makes it harder for unintentional changes to expand the project mid-cycle.<\/td><td class=\"column-2\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3924 from cache -->\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-8\">\n<h2 class=\"h2 text-block__title\">How to use the MoSCoW method in 5 steps<\/h2>\n<p>Knowing the categories is one thing; running the method with a real team is another. The process below turns MoSCoW from a definition into a repeatable working session. Follow these 5 steps to move from a messy backlog to an agreed plan.<\/p>\n<ol>\n<li><a href=\"https:\/\/monday.com\/blog\/productivity\/requirements-gathering-template\/\"><strong>Gather requirements<\/strong><\/a><strong> and align stakeholders:<\/strong> List every task, feature, or requirement in one place, then bring the people who own delivery and the people who own outcomes into the same conversation.<\/li>\n<li><strong>Agree the classification criteria first:<\/strong> Define what &#8220;must-have&#8221; actually means for this release before you sort anything. A shared definition prevents every stakeholder from labeling their own request a must.<\/li>\n<li><strong>Sort each item into a category:<\/strong> Work through the list and place each item into must, should, could, or won&#8217;t-have. Challenge every must with the question, &#8220;what happens if we don&#8217;t deliver this?&#8221;<\/li>\n<li><strong>Balance the effort:<\/strong> Check that must-haves don&#8217;t swallow the whole timebox. Keep must-have work to around 60% of effort and hold a pool of could-haves as contingency.<\/li>\n<li><strong>Review and revisit each cycle:<\/strong> Priorities shift as you learn more, so revisit the classification at the start of each timebox and move items between categories as needed.<\/li>\n<\/ol>\n<p>The hardest part is keeping the agreed list from gradually changing after the meeting ends. A shared board with a priority column keeps everyone working from the same classification, so a should-have doesn&#8217;t get promoted to a must-have without a visible decision.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-9\">\n<h2 class=\"h2 text-block__title\">MoSCoW prioritization example<\/h2>\n<p>Here&#8217;s how a team launching a new web app might use MoSCoW to sort features. The table below shows 4 features placed into categories, with a short rationale for each decision.<\/p>\n\n<table id=\"tablepress-3925\" class=\"tablepress tablepress-id-3925\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Feature<\/th><th class=\"column-2\">Category<\/th><th class=\"column-3\">Rationale<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Secure user login and checkout<\/td><td class=\"column-2\">Must-have<\/td><td class=\"column-3\">The launch is unsafe and can't transact without it<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Password reset by email<\/td><td class=\"column-2\">Should-have<\/td><td class=\"column-3\">Important, but support can reset accounts manually at first<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Dark mode theme<\/td><td class=\"column-2\">Could-have<\/td><td class=\"column-3\">A small uplift that's the first to drop if time runs short<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Native mobile app<\/td><td class=\"column-2\">Won't-have (this time)<\/td><td class=\"column-3\">Deferred to a later release, not rejected<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\"><\/td><td class=\"column-2\"><\/td><td class=\"column-3\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3925 from cache -->\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-10\">\n<h2 class=\"h2 text-block__title\">MoSCoW best practices for balancing priorities<\/h2>\n<p>The method only works if the categories stay disciplined. When everything drifts into must-have, MoSCoW stops protecting the deadline. These best practices keep the balance realistic and the plan deliverable.<\/p>\n<ul>\n<li><strong>Agree your criteria before sorting:<\/strong> Decide what qualifies as a must-have first, so the definition drives the decision rather than the loudest voice in the room.<\/li>\n<li><strong>Balance effort, not item count:<\/strong> According to the <a href=\"https:\/\/www.agilebusiness.org\/resource\/what-is-moscow-prioritization\/\">Agile Business Consortium&#8217;s DSDM guidance<\/a>, keep must-have work to no more than about 60% of the timebox&#8217;s effort and hold roughly 20% as could-have contingency.<\/li>\n<li><strong>Prioritize within a category too:<\/strong> Not all must-haves are equal, so rank the order of delivery inside each category as well as across them.<\/li>\n<li><strong>Revisit every timebox:<\/strong> Re-sort the list at the start of each cycle, because a could-have can become a must-have as circumstances change.<\/li>\n<li><strong>Make won&#8217;t-have decisions visible:<\/strong> Record what you&#8217;re deferring and where everyone can see it, so exclusions are a shared decision rather than a surprise.<\/li>\n<\/ul>\n\n<img width=\"1024\" height=\"640\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/to-do-list-1024x640.jpg\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/to-do-list-1024x640.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/to-do-list-300x188.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/to-do-list-768x480.jpg 768w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/to-do-list.jpg 1280w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-11\">\n<h2 class=\"h2 text-block__title\">Manage MoSCoW prioritization with the AI Workspace<\/h2>\n<p>A MoSCoW list is only useful if it stays current and visible as work moves. Static spreadsheets fall out of date the moment priorities shift, and no one notices until the deadline is at risk.<\/p>\n<p><\/p>\n<p>&nbsp;<\/p>\n<p>monday AI Workspace keeps prioritization live, connected to the work, and shared across every team involved.<\/p>\n<ul>\n<li><strong>Priority columns and board views:<\/strong> Start with a priority column and board views such as <a href=\"https:\/\/monday.com\/blog\/project-management\/kanban-methodology\/\">Kanban<\/a> and table to sort each item into must, should, could, or won&#8217;t-have. Dashboards then roll those decisions up into a real-time picture of how effort is distributed across the 4 categories, so you can spot a bloated must-have list before it derails the timebox. You can also <a href=\"https:\/\/monday.com\/blog\/project-management\/action-priority-matrix-vs-eisenhower-matri\/\">prioritize tasks using matrices<\/a> and task prioritization templates to compare items side by side.<\/li>\n<li><strong>Automations for routine upkeep:<\/strong> When an item&#8217;s priority changes, an automation can notify the owner, move the item to the right group, or flag it for review, so the classification doesn&#8217;t change. These same <a href=\"https:\/\/monday.com\/blog\/productivity\/prioritization-tools\/\">prioritization tools<\/a> keep stakeholders aligned without another status meeting, and they connect to your broader <a href=\"https:\/\/monday.com\/blog\/project-management\/guide-to-task-management\/\">task management<\/a> process.<\/li>\n<li><a href=\"https:\/\/monday.com\/w\/sidekick\"><strong>monday sidekick<\/strong><\/a><strong> for AI-assisted sorting:<\/strong> monday sidekick is a context-aware assistant that can recommend how to sort a backlog, draft the classification criteria, and answer questions about your boards in plain language. As you scale, Sidekick helps keep the effort balance in view rather than buried in a spreadsheet.<\/li>\n<li><strong>monday agents for high-volume prioritization:<\/strong> For repeatable, high-volume prioritization, monday agents are task-specific AI workers that act inside your boards. The <a href=\"https:\/\/monday.com\/w\/ai-templates\/ai-agents\/sprint-planner-agent\">Sprint Planner<\/a> organizes your backlog and drafts sprint goals around your team&#8217;s capacity, giving you a starting point for what fits in the timebox. The <a href=\"https:\/\/monday.com\/w\/ai-templates\/ai-agents\/dependency-and-risk-mapper\">Dependency and Risk Mapper<\/a> traces dependency chains and flags where a slip could cascade, covering the sequencing gap MoSCoW doesn&#8217;t handle on its own. Agents work alongside your team rather than replacing anyone, so people keep the final call on what&#8217;s a must-have. Every agent runs on mondayDB, one connected data layer spanning marketing, sales, ops, IT, HR, product, and legal, with 200+ integrations and MCP keeping the rest of your stack in sync.<\/li>\n<\/ul>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"2\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-12\">\n<h2 class=\"h2 text-block__title\">Transform MoSCoW priorities into real progress<\/h2>\n<p>The\u00a0real value of the MoSCoW method isn&#8217;t the four labels; it&#8217;s the clarity they force. When your team agrees what&#8217;s a must-have and what&#8217;s deferred, you protect the deadline and ship the work that actually matters. That shared honesty is what keeps scope creep from swallowing the release.<\/p>\n<p>The next step is keeping those priorities alive as conditions change. Pairing the MoSCoW method with AI-assisted scoring and risk detection lets you re-sort the list the moment reality shifts, instead of once a quarter. On <a href=\"https:\/\/monday.com\/blog\/product\/work-os\/\">a connected work platform<\/a>, your priorities move as fast as your work does.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"3\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-13\">\n<div class=\"accordion faq\" id=\"faq-moscow-method-faqs\">\n  <h2 class=\"accordion__heading section-title text-left\">MoSCoW method FAQs<\/h2>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-1\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What does MoSCoW stand for?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>MoSCoW stands for must-have, should-have, could-have, and won't-have (this time). Each term is a priority category. The lowercase Os are filler letters added only to make the acronym easier to say, so they carry no meaning of their own.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-2\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Who created the MoSCoW method?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>The MoSCoW method was created by software developer Dai Clegg in 1994. He designed it to help teams prioritize requirements during rapid, timeboxed development, and it was later documented in the Dynamic System Development Method (DSDM) handbook.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-3\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Is MoSCoW an Agile technique?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>Yes, MoSCoW is an Agile technique closely tied to the DSDM framework maintained by the Agile Business Consortium. It suits timeboxed delivery because it fixes priorities before a cycle begins, helping Agile teams decide what to include in a sprint or release.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-4\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the disadvantages of the MoSCoW method?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>The main disadvantages of the MoSCoW method are subjectivity and limited ranking. Categorization relies on judgment rather than numbers, so teams can disagree on what counts as a must-have. It also doesn't rank within categories on its own or account for task dependencies.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-5\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What percentage of tasks should be must-have?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-5\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>DSDM guidance recommends keeping must-have requirements to no more than roughly 60% of a timebox's effort. The remaining effort covers should-haves and a contingency pool of about 20% could-haves, which gives the team room to absorb delays without missing the deadline.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-6\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How does monday AI Workspace support MoSCoW prioritization?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-6\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>monday AI Workspace supports MoSCoW prioritization with priority columns, board views, and dashboards that keep every category visible in real time. Automations update priorities as work changes, while Sidekick and agents help sort backlogs and flag risks, so people keep the final decision.<\/p>\n    <\/div>\n  <\/div>\n  {\n    \"@context\": \"https:\\\/\\\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What does MoSCoW stand for?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>MoSCoW stands for must-have, should-have, could-have, and won't-have (this time). Each term is a priority category. The lowercase Os are filler letters added only to make the acronym easier to say, so they carry no meaning of their own.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Who created the MoSCoW method?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The MoSCoW method was created by software developer Dai Clegg in 1994. He designed it to help teams prioritize requirements during rapid, timeboxed development, and it was later documented in the Dynamic System Development Method (DSDM) handbook.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Is MoSCoW an Agile technique?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Yes, MoSCoW is an Agile technique closely tied to the DSDM framework maintained by the Agile Business Consortium. It suits timeboxed delivery because it fixes priorities before a cycle begins, helping Agile teams decide what to include in a sprint or release.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are the disadvantages of the MoSCoW method?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The main disadvantages of the MoSCoW method are subjectivity and limited ranking. Categorization relies on judgment rather than numbers, so teams can disagree on what counts as a must-have. It also doesn't rank within categories on its own or account for task dependencies.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What percentage of tasks should be must-have?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>DSDM guidance recommends keeping must-have requirements to no more than roughly 60% of a timebox's effort. The remaining effort covers should-haves and a contingency pool of about 20% could-haves, which gives the team room to absorb delays without missing the deadline.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How does monday AI Workspace support MoSCoW prioritization?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>monday AI Workspace supports MoSCoW prioritization with priority columns, board views, and dashboards that keep every category visible in real time. Automations update priorities as work changes, while Sidekick and agents help sort backlogs and flag risks, so people keep the final decision.\\n\"\n            }\n        }\n    ]\n}<\/div>\n\n\n<\/div>","protected":false,"raw":"<figure style=\"text-align: center;\"><\/figure>\r\nWhen developing a new product or embarking on a new project, it can be difficult to decide which elements to include and which are more expendable. Prioritizing tasks is usually a team effort, requiring input from everyone involved in the project setup. Getting a clear idea of which elements should take the lead from the start can help you to avoid hiccups later on. For this reason, using the MoSCoW prioritization method, which is a part of the Agile methodology, to categorize project elements based on importance can be helpful for getting started and ensuring a viable product that enhances user experience.\r\n\r\nThe MoSCoW prioritization method is a tool that can be used to prioritize projects, initiatives, or tasks. It is especially useful when there are many competing demands and it is not possible to do everything at once. Using monday.com's Work OS, you can quickly and easily break down projects into simple tasks and their priorities. Now, let's discuss\u00a0everything you need to know about using this method.\r\n<p class=\"p1\">[cta-button url=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\"]Try work management[\/cta-button]<\/p>\r\n\r\n<h2><strong>What is the MoSCoW prioritization method?<\/strong><\/h2>\r\n<blockquote>MoSCoW prioritization is a tool for creating a hierarchy of priorities before and during a project. It stems from the Agile project management method, which aims to establish elements like product cost, quality, and project requirements as early as possible.<\/blockquote>\r\nMoSCoW is an acronym for \"must-have,\" \"should-have,\" \"could-have,\" and \"won't-have (this time).\" Each item in the acronym denotes a category of prioritization. The idea is that items are categorized at the beginning of a project to clarify what is strictly necessary, what is desirable, and what the project can do without. Before we get deeper into the categories, let's take a look at where this method came from.\r\n<h2><strong>Where does the term MoSCoW come from?<\/strong><\/h2>\r\nThe term MoSCoW comes originated with software developer Dai Clegg, who created the method when he was working at Oracle. To help his team prioritize tasks during development work on <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">product releases<\/a>, he devised the MoSCoW technique. The acronym includes lowercase Os between consonants to make it easier to pronounce.\r\n\r\n[twitter]Software developer Dai Clegg created the MoSCoW method during his time working at Oracle. He designed the Moscow prioritization technique to help his team prioritize tasks during developmental work on product releases.[\/twitter]\r\n\r\nYou can now find a detailed account of how to use the MoSCoW method in the Dynamic System Development Method (DSDM) handbook. The MoSCoW method can be used to prioritize project requirements, product features, or any other project elements. When using the MoSCoW method, each element is assigned to one of the four prioritization categories based on its importance to the project. Now, let's take a closer look at the prioritization categories and how to use them.\r\n\r\n<strong>Learn more<\/strong>: <a href=\"https:\/\/monday.com\/w\/ai-templates\/ai-agents\/chief-of-staff-agent\">AI Chief of Staff agent<\/a>\r\n<h2><strong>What are the categories within the MoSCoW prioritization method?<\/strong><\/h2>\r\nAs mentioned previously, the acronym \"MoSCoW\"\u00a0stands for \"must-have,\" \"should-have,\" \"could-have,\" and \"won't-have (this time).\"\r\n<ul>\r\n \t<li><strong>Must-have:<\/strong>\u00a0These items are essential for the success of the project. There can be no compromise on whether they are included, because without them, the entire project would be meaningless. In short, this is a top-priority MoSCoW requirement.<\/li>\r\n \t<li><strong>Should-have:<\/strong>\u00a0These items are those that are important but not absolutely essential like those in the \"must-have\" category. Elements in this category are considered a secondary priority; that is, they are important, but not crucial to success.<\/li>\r\n \t<li><strong>Could-have:<\/strong> These items would be nice to have but are not essential. Still less important than the two preceding categories, these elements are considered a third-level priority. If including them will have negative consequences on cost or meeting deadlines, they should be omitted. It is only when they don't negatively affect other project elements that they should be included.<\/li>\r\n \t<li><strong>Won't-have (this time):<\/strong> These items are those that are not essential and can be excluded from the project without jeopardizing its success. Being the lowest priority category, omitting them won't hurt the project and they can be included when project conditions are more favorable.<\/li>\r\n<\/ul>\r\n<h2><strong>When should you use the MoSCoW prioritization method?<\/strong><\/h2>\r\nThe advantage of the MoSCoW method is that it can be applied to a wide range of situations, both in personal and professional contexts. For instance, an individual might use the method to prioritize their workload for the week or a team might use it to identify which tasks need to be completed first to meet a looming deadline. In general, the MoSCoW method is most useful when an individual or project team is facing a large number of tasks and needs help deciding which ones to focus on first. Additionally, if you're starting a project and are unsure which elements should take priority, you can get your project team together and use the MoSCoW method as a discussion tool in your prioritization process.\r\n\r\nHowever, it should be noted that the method does have some limitations. For instance, it doesn't account for task dependencies or other factors that might impact the order in which tasks should be completed. As such, it should be used as one tool in a broader arsenal of task-management strategies.\r\n\r\n[cta-button url=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\"]Try work management[\/cta-button]\r\n<h3><strong>MoSCoW method: the pros and cons<\/strong><\/h3>\r\nBecause the framework makes it possible to manage the requirements for a given product release, it's extremely common among Agile projects with set timeboxes. Within project management, this prioritization technique has demonstrated its effectiveness and dependability. Of course, it isn't flawless \u2014 an objective look can help highlight shortcomings as well as benefits of the MoSCoW method. Let's examine its pros and cons.\r\n<h4><em>Pros<\/em><\/h4>\r\n<ul>\r\n \t<li><strong>Easy to master:\u00a0<\/strong>The method is based on very simple principles that are easy to understand, so you won't need to do much background research before getting started.<\/li>\r\n \t<li><strong>Helps prioritize:\u00a0<\/strong>It helps to clearly visualize priorities and sort them into a hierarchy. This way, you'll never need to be confused about which elements are more or less important than others.<\/li>\r\n \t<li><strong>Useful for team discussions:\u00a0<\/strong>Using the MoSCoW method in group discussions can be a great way to get team members to open up about their ideas. It can serve as a conversation starter, putting everyone on the same page.<\/li>\r\n \t<li><strong>Helps achieve stakeholder consensus:\u00a0<\/strong>When used among stakeholders, it can be a good way to reach an agreement between stakeholders on which elements should take priority. When stakeholders are present during the categorization process, this improves their understanding of the project.<\/li>\r\n \t<li><strong>Can prevent scope creep:\u00a0<\/strong>Scope creep is when unintentional changes occur during project execution. By setting clear and fixed priorities at the beginning, scope creep can be prevented.<\/li>\r\n<\/ul>\r\n<h4><em>Cons<\/em><\/h4>\r\n<ul>\r\n \t<li><strong>Priority requirements can be subjective:\u00a0<\/strong>Since the categorization procedure is not based on numerical data, it leaves room for subjective interpretation. This can manifest as conflicting ideas about which elements should take the lead and which are less important.<\/li>\r\n \t<li><strong>Items require background context:<\/strong>\u00a0To accurately categorize each element, you'll need to provide context for each of them. This may be time-consuming and tedious.<\/li>\r\n \t<li><strong>Doesn't account for possible change:\u00a0<\/strong>Putting items into a fixed category doesn't allow you to account for possible changes that occur during project execution. For example, elements that are not necessary at the start may become crucial down the line based on extraneous changes in circumstance.<\/li>\r\n<\/ul>\r\n<h2><strong>Examples of the MoSCoW prioritization method in practice\u00a0<\/strong><\/h2>\r\nImagine that a <a href=\"https:\/\/monday.com\/templates\/template\/38817\/software-development\">software development<\/a>\u00a0product manager is developing a new cloud-based workspace for individuals and organizations to improve their workflow. They're trying to decide which features are most important, which would be nice, and which probably won't make it into this specific release. They decide that cloud storage is a must-have feature, otherwise, it wouldn't be cloud-based, and they would be completely missing their target. Once the must-haves are identified, they are further broken down into smaller tasks, or \"should-haves\". These should-haves are then prioritized according to their importance. Finally, the remaining tasks are classified as either \"could-haves\" or \"won't-haves.\"\r\n\r\nAnother example involves a marketing team who are trying to prioritize tasks for their next <a href=\"https:\/\/monday.com\/blog\/marketing\/go-to-market-strategy\/\">marketing strategy<\/a>. Seeing as the vast majority of their sales come from email marketing, they list this as a top priority. Their second biggest number of sales comes from Instagram marketing, so they categorize this as a secondary priority, and so on.\r\n<h2><strong>Executing task prioritization on monday.com<\/strong><\/h2>\r\nmonday.com is a great tool for managing tasks and priorities. With its sleek interface and simple task management system, it's easy to see why so many people use it. However, one of its most important features is the ability to <a href=\"https:\/\/monday.com\/blog\/project-management\/action-priority-matrix-vs-eisenhower-matri\/\">prioritize tasks using matrices and task prioritization templates<\/a>. This is especially useful for professionals and product managers who need to make sure they're focusing on what's important. monday.com makes it easy to share tasks and priorities with others, so you can be sure that team members, stakeholders and development teams are on the same page. With its convenient features and simple task management system, monday.com is the perfect tool for anyone, especially project teams, who need to prioritize their tasks.\r\n<p class=\"p1\">[cta-button url=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\"]Try work management[\/cta-button]<\/p>\r\n\r\n<h2><strong>Getting priorities straight<\/strong><\/h2>\r\nThe MoSCoW prioritization method can be adapted to different situations and organizations, making it a versatile tool for decision-making. The advantages of using this method are that it's simple to use, it can help spark discussions between team members, and it gets stakeholders on the same page.\u00a0monday.com offers a range of prioritization matrices to help you hierarchically structure task importance and get work done in the most optimal way. Our feature-rich Work OS offers everything you and your team need to streamline your digital workflow and meet your business objectives.\r\n\r\n[faq id=\"moscowprioritization\"]\r\n<div style=\"text-align: right;\"><\/div>"},"excerpt":{"rendered":"<p>When developing a new product or embarking on a new project, it can be difficult to decide which elements to include and which are more expendable. Prioritizing tasks is usually a team effort, requiring input from everyone involved in the project setup. Getting a clear idea of which elements should &#8230;<\/p>\n","protected":false},"author":219,"featured_media":364100,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"pages\/cornerstone-primary.php","format":"standard","meta":{"_acf_changed":false,"monday_item_id":18041079554,"monday_board_id":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[13904],"tags":[],"class_list":["post-108380","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management"],"acf":{"lobby_image":false,"post_thumbnail_title":"","hide_post_info":false,"hide_bottom_cta":false,"hide_from_blog":false,"landing_page_layout":false,"cluster":"","display_dates":"updated","featured_image_link":"","banner_url":"","main_text_banner":"Try monday.com for projects","sub_title_banner":"Join the 152K+ customers who use monday.com","sub_title_banner_second":"","banner_button_text":"","below_banner_line":"","use_customized_cta":false,"display_subscribe_widget":false,"custom_schema_code":"<script type=\"application\/ld+json\">\r\n{\r\n  \"@context\": \"https:\/\/schema.org\",\r\n  \"@type\": \"DefinedTerm\",\r\n  \"name\": \"MoSCoW prioritization method\",\r\n  \"description\": \"MoSCoW prioritization is a tool for creating a hierarchy of priorities before and during a project. It stems from the Agile project management method, which aims to establish elements like product cost, quality, and project requirements as early as possible.\"\r\n}\r\n<\/script>","sidebar_color_banner":"","custom_tags":false,"faqs":[{"faq_title":"MoSCoW method FAQs","faq_shortcode":"moscow-method-faqs","faq":[{"question":"What does MoSCoW stand for?","answer":"<p>MoSCoW stands for must-have, should-have, could-have, and won't-have (this time). Each term is a priority category. The lowercase Os are filler letters added only to make the acronym easier to say, so they carry no meaning of their own.<\/p>\n"},{"question":"Who created the MoSCoW method?","answer":"<p>The MoSCoW method was created by software developer Dai Clegg in 1994. He designed it to help teams prioritize requirements during rapid, timeboxed development, and it was later documented in the Dynamic System Development Method (DSDM) handbook.<\/p>\n"},{"question":"Is MoSCoW an Agile technique?","answer":"<p>Yes, MoSCoW is an Agile technique closely tied to the DSDM framework maintained by the Agile Business Consortium. It suits timeboxed delivery because it fixes priorities before a cycle begins, helping Agile teams decide what to include in a sprint or release.<\/p>\n"},{"question":"What are the disadvantages of the MoSCoW method?","answer":"<p>The main disadvantages of the MoSCoW method are subjectivity and limited ranking. Categorization relies on judgment rather than numbers, so teams can disagree on what counts as a must-have. It also doesn't rank within categories on its own or account for task dependencies.<\/p>\n"},{"question":"What percentage of tasks should be must-have?","answer":"<p>DSDM guidance recommends keeping must-have requirements to no more than roughly 60% of a timebox's effort. The remaining effort covers should-haves and a contingency pool of about 20% could-haves, which gives the team room to absorb delays without missing the deadline.<\/p>\n"},{"question":"How does monday AI Workspace support MoSCoW prioritization?","answer":"<p>monday AI Workspace supports MoSCoW prioritization with priority columns, board views, and dashboards that keep every category visible in real time. Automations update priorities as work changes, while Sidekick and agents help sort backlogs and flag risks, so people keep the final decision.<\/p>\n"}]}],"activate_cta_banner":true,"cta_banner_text":"<p><strong>Don\u2019t miss <\/strong> more quality content!<\/p>\n","hide_time_to_read":false,"cornerstone_hero_cta_override":{"label":"","url":""},"show_contact_sales_button":"default","override_contact_sales_label":"","override_contact_sales_url":"","custom_header_banner":false,"menu_cta_override":{"label":"","url":""},"parse_from_google_doc":false,"sections":[{"acf_fc_layout":"content_1","blocks":[{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<p>Every team faces more requests than it can deliver in the time available. And when everything looks urgent, it can be tempting to promise to deliver all of it, even though you know there&#8217;s a strong risk you&#8217;ll miss the deadline. The MoSCoW method gives you a shared, honest way to decide what ships now and what waits.<\/p>\n<p>This guide breaks down the 4 MoSCoW categories, where the framework came from, and how to run it step by step. You&#8217;ll also see a worked prioritization matrix, the effort-balancing rules that keep releases realistic, and how to manage the whole process on monday AI Workspace.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"1\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":"<ul>\n<li>The MoSCoW method sorts work into 4 priority categories: must-have, should-have, could-have, and won&#8217;t-have (this time).<\/li>\n<li>It comes from the Agile DSDM framework and works best inside a fixed timebox or <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">release cycle<\/a>.<\/li>\n<li>The won&#8217;t-have category is the method&#8217;s key strength, because naming exclusions upfront prevents <a href=\"https:\/\/monday.com\/blog\/project-management\/keep-scope-creep-undermining-project\/\">scope creep<\/a>.<\/li>\n<li>DSDM recommends keeping must-have work to about 60% of effort and holding roughly 20% as could-have contingency.<\/li>\n<li>On monday AI Workspace, priority columns, dashboards, and AI agents keep every MoSCoW decision visible and current as work shifts.<\/li>\n<\/ul>\n"},{"acf_fc_layout":"image","image_type":"normal","image":363922,"image_link":""}]},{"main_heading":"What is the MoSCoW method?","content_block":[{"acf_fc_layout":"text","content":"<p>MoSCoW prioritization is a tool for creating a hierarchy of priorities before and during a project. It stems from the <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-project-management\/\">Agile project management method<\/a>, which aims to establish elements like product cost, quality, and project requirements as early as possible.<\/p>\n<p>MoSCoW stands for must-have, should-have, could-have, and won&#8217;t-have (this time). Each item in the acronym denotes a category of prioritization. The idea is that items are sorted at the start of a project to clarify what is strictly necessary, what is desirable, and what the project can do without.<\/p>\n<p>You&#8217;ll also see the approach called the MoSCoW framework or the MoSCoW model, but the mechanics are the same in every version. It&#8217;s a fast, low-jargon way to turn a long list of competing demands into an agreed order of delivery that your whole team can read at a glance.<\/p>\n"}]},{"main_heading":"Where does the MoSCoW method come from?","content_block":[{"acf_fc_layout":"text","content":"<p><a href=\"https:\/\/monday.com\/blog\/rnd\/software-development-process\/\">Software developer<\/a> Dai Clegg created the MoSCoW method in 1994 for use in rapid application development (RAD). A <a href=\"https:\/\/arxiv.org\/abs\/2402.13149\">2024 requirements-prioritization survey<\/a> attributes its introduction to Clegg while he was at Oracle UK. He designed it to help teams agree on priorities quickly during <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-release-planning\/\">product releases<\/a>.<\/p>\n<p>The lowercase Os carry no meaning and exist only to make the acronym easier to pronounce. Practitioners then used it extensively within the Dynamic System Development Method (DSDM) from 2002 onward. The DSDM Consortium, now the Agile Business Consortium, adopted and documented the method, and it maintains the canonical definition today.<\/p>\n<p>Clegg built MoSCoW for fast, timeboxed cycles where time and resources are fixed and scope has to flex.\u00a0Understanding its origin helps you apply it where it performs best \u2014 release planning and sprint scoping.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":363489,"image_link":""}]},{"main_heading":"What do the 4 MoSCoW categories mean?","content_block":[{"acf_fc_layout":"text","content":"<p>The four MoSCoW categories are the heart of the method. Each one answers a single question: how badly does the project need this item to succeed? Here&#8217;s what each category means, using the standard definitions.<\/p>\n<ul>\n<li><strong>Must-have:<\/strong>\u00a0These items are essential for the <a href=\"https:\/\/monday.com\/blog\/project-management\/how-to-define-project-success\/\">success of the project<\/a>. There can be no compromise on whether they are included, because without them, the entire project would be meaningless. In short, this is a top-priority MoSCoW requirement.<\/li>\n<li><strong>Should-have<\/strong>:\u00a0These items are those that are important but not absolutely essential like those in the &#8220;must-have&#8221; category. Elements in this category are considered a secondary priority; that is, they are important, but not crucial to success.<\/li>\n<li><strong>Could-have<\/strong>: These items would be nice to have but are not essential. Still less important than the two preceding categories, these elements are considered a third-level priority. If including them will have negative consequences on cost or meeting deadlines, they should be omitted. It is only when they don&#8217;t negatively affect other project elements that they should be included.<\/li>\n<li><strong>Won&#8217;t-have (this time)<\/strong>: These items are those that are not essential and can be excluded from the project without jeopardizing its success. Being the lowest priority category, omitting them won&#8217;t hurt the project and they can be included when project conditions are more favorable. Note that most teams rush past won&#8217;t-have, but it does the heavy lifting. Naming what you won&#8217;t build this time, helps you make exclusions explicit and visible to stakeholders. That single act of writing it down is the strongest defense you have against scope creep later in the cycle.<\/li>\n<\/ul>\n"}]},{"main_heading":"When should you use the MoSCoW method?","content_block":[{"acf_fc_layout":"text","content":"<p>MoSCoW works best in specific situations where time is fixed and you need to make fast, shared decisions about what ships. Use it when:<\/p>\n<ul>\n<li><strong>You&#8217;re planning a timeboxed release or sprint:<\/strong> MoSCoW was built for fixed cycles where scope has to flex, so it&#8217;s ideal for Agile teams deciding what fits in the next iteration.<\/li>\n<li><strong>Stakeholders disagree on what&#8217;s urgent:<\/strong> When everyone thinks their request is critical, MoSCoW forces a shared conversation about what the project actually needs to succeed.<\/li>\n<li><strong>You&#8217;re facing more requests than capacity:<\/strong> If your backlog is longer than your timeline, MoSCoW helps you draw a clear line between what you&#8217;ll deliver now and what waits.<\/li>\n<li><strong>Scope creep is threatening the deadline:<\/strong> The won&#8217;t-have category makes exclusions explicit and visible, so new requests don&#8217;t quietly expand the plan mid-cycle.<\/li>\n<li><strong>You need a fast prioritization framework:<\/strong> MoSCoW doesn&#8217;t require scoring models or complex calculations, so you can sort a backlog in a single working session.<\/li>\n<li><strong>You&#8217;re kicking off a project and priorities are unclear:<\/strong> Use MoSCoW as a discussion tool to align your team on what matters most before work begins.<\/li>\n<\/ul>\n<p>But MoSCoW doesn&#8217;t handle everything. It doesn&#8217;t account for task dependencies, technical sequencing, or factors that might shift the order of delivery. Use it as one tool in a broader set of prioritization and task-management strategies, such as RICE or <a href=\"https:\/\/monday.com\/templates\/eisenhower-matrix\">Eisenhower<\/a>, not as a replacement for planning the how.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":363456,"image_link":""}]},{"main_heading":"MoSCoW method: the pros and cons","content_block":[{"acf_fc_layout":"text","content":"<p>MoSCoW is widely used in Agile projects with fixed timeboxes because it helps teams manage release requirements quickly. It&#8217;s proven effective, but it&#8217;s not perfect. The table below breaks down where the method delivers value and where it falls short.<\/p>\n\n<table id=\"tablepress-3924\" class=\"tablepress tablepress-id-3924\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Pros<\/th><th class=\"column-2\">Cons<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Easy to master: The method uses simple principles that require little background research to understand and apply.<\/td><td class=\"column-2\">Priority requirements can be subjective: Categorization relies on judgment rather than numerical data, which can lead to conflicting opinions about what qualifies as a must-have.<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Helps prioritize: It creates a clear visual hierarchy of priorities, so teams always know which elements matter most.<\/td><td class=\"column-2\">Items require background context: Accurate categorization demands context for each item, which can be time-consuming and tedious to gather.<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Useful for team discussions: MoSCoW serves as a conversation starter that gets team members aligned and sharing ideas openly.<\/td><td class=\"column-2\">Doesn't account for change: Fixed categories don't adapt when circumstances shift mid-project, so an item that's not necessary at the start may become critical later.<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Helps achieve stakeholder consensus: When stakeholders participate in categorization, they gain a shared understanding of the project and agree on what takes priority.<\/td><td class=\"column-2\"><\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Can prevent scope creep: Setting clear, fixed priorities at the start makes it harder for unintentional changes to expand the project mid-cycle.<\/td><td class=\"column-2\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3924 from cache -->\n"}]},{"main_heading":"How to use the MoSCoW method in 5 steps","content_block":[{"acf_fc_layout":"text","content":"<p>Knowing the categories is one thing; running the method with a real team is another. The process below turns MoSCoW from a definition into a repeatable working session. Follow these 5 steps to move from a messy backlog to an agreed plan.<\/p>\n<ol>\n<li><a href=\"https:\/\/monday.com\/blog\/productivity\/requirements-gathering-template\/\"><strong>Gather requirements<\/strong><\/a><strong> and align stakeholders:<\/strong> List every task, feature, or requirement in one place, then bring the people who own delivery and the people who own outcomes into the same conversation.<\/li>\n<li><strong>Agree the classification criteria first:<\/strong> Define what &#8220;must-have&#8221; actually means for this release before you sort anything. A shared definition prevents every stakeholder from labeling their own request a must.<\/li>\n<li><strong>Sort each item into a category:<\/strong> Work through the list and place each item into must, should, could, or won&#8217;t-have. Challenge every must with the question, &#8220;what happens if we don&#8217;t deliver this?&#8221;<\/li>\n<li><strong>Balance the effort:<\/strong> Check that must-haves don&#8217;t swallow the whole timebox. Keep must-have work to around 60% of effort and hold a pool of could-haves as contingency.<\/li>\n<li><strong>Review and revisit each cycle:<\/strong> Priorities shift as you learn more, so revisit the classification at the start of each timebox and move items between categories as needed.<\/li>\n<\/ol>\n<p>The hardest part is keeping the agreed list from gradually changing after the meeting ends. A shared board with a priority column keeps everyone working from the same classification, so a should-have doesn&#8217;t get promoted to a must-have without a visible decision.<\/p>\n"}]},{"main_heading":"MoSCoW prioritization example","content_block":[{"acf_fc_layout":"text","content":"<p>Here&#8217;s how a team launching a new web app might use MoSCoW to sort features. The table below shows 4 features placed into categories, with a short rationale for each decision.<\/p>\n\n<table id=\"tablepress-3925\" class=\"tablepress tablepress-id-3925\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Feature<\/th><th class=\"column-2\">Category<\/th><th class=\"column-3\">Rationale<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Secure user login and checkout<\/td><td class=\"column-2\">Must-have<\/td><td class=\"column-3\">The launch is unsafe and can't transact without it<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Password reset by email<\/td><td class=\"column-2\">Should-have<\/td><td class=\"column-3\">Important, but support can reset accounts manually at first<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Dark mode theme<\/td><td class=\"column-2\">Could-have<\/td><td class=\"column-3\">A small uplift that's the first to drop if time runs short<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Native mobile app<\/td><td class=\"column-2\">Won't-have (this time)<\/td><td class=\"column-3\">Deferred to a later release, not rejected<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\"><\/td><td class=\"column-2\"><\/td><td class=\"column-3\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3925 from cache -->\n"}]},{"main_heading":"MoSCoW best practices for balancing priorities","content_block":[{"acf_fc_layout":"text","content":"<p>The method only works if the categories stay disciplined. When everything drifts into must-have, MoSCoW stops protecting the deadline. These best practices keep the balance realistic and the plan deliverable.<\/p>\n<ul>\n<li><strong>Agree your criteria before sorting:<\/strong> Decide what qualifies as a must-have first, so the definition drives the decision rather than the loudest voice in the room.<\/li>\n<li><strong>Balance effort, not item count:<\/strong> According to the <a href=\"https:\/\/www.agilebusiness.org\/resource\/what-is-moscow-prioritization\/\">Agile Business Consortium&#8217;s DSDM guidance<\/a>, keep must-have work to no more than about 60% of the timebox&#8217;s effort and hold roughly 20% as could-have contingency.<\/li>\n<li><strong>Prioritize within a category too:<\/strong> Not all must-haves are equal, so rank the order of delivery inside each category as well as across them.<\/li>\n<li><strong>Revisit every timebox:<\/strong> Re-sort the list at the start of each cycle, because a could-have can become a must-have as circumstances change.<\/li>\n<li><strong>Make won&#8217;t-have decisions visible:<\/strong> Record what you&#8217;re deferring and where everyone can see it, so exclusions are a shared decision rather than a surprise.<\/li>\n<\/ul>\n"},{"acf_fc_layout":"image","image_type":"normal","image":355237,"image_link":""}]},{"main_heading":"Manage MoSCoW prioritization with the AI Workspace","content_block":[{"acf_fc_layout":"text","content":"<p>A MoSCoW list is only useful if it stays current and visible as work moves. Static spreadsheets fall out of date the moment priorities shift, and no one notices until the deadline is at risk.<\/p>\n<p><iframe loading=\"lazy\" title=\"Welcome your AI agents to the team | The AI Work Platform by monday.com\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/PGlkti0nF9k?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n<p>&nbsp;<\/p>\n<p>monday AI Workspace keeps prioritization live, connected to the work, and shared across every team involved.<\/p>\n<ul>\n<li><strong>Priority columns and board views:<\/strong> Start with a priority column and board views such as <a href=\"https:\/\/monday.com\/blog\/project-management\/kanban-methodology\/\">Kanban<\/a> and table to sort each item into must, should, could, or won&#8217;t-have. Dashboards then roll those decisions up into a real-time picture of how effort is distributed across the 4 categories, so you can spot a bloated must-have list before it derails the timebox. You can also <a href=\"https:\/\/monday.com\/blog\/project-management\/action-priority-matrix-vs-eisenhower-matri\/\">prioritize tasks using matrices<\/a> and task prioritization templates to compare items side by side.<\/li>\n<li><strong>Automations for routine upkeep:<\/strong> When an item&#8217;s priority changes, an automation can notify the owner, move the item to the right group, or flag it for review, so the classification doesn&#8217;t change. These same <a href=\"https:\/\/monday.com\/blog\/productivity\/prioritization-tools\/\">prioritization tools<\/a> keep stakeholders aligned without another status meeting, and they connect to your broader <a href=\"https:\/\/monday.com\/blog\/project-management\/guide-to-task-management\/\">task management<\/a> process.<\/li>\n<li><a href=\"https:\/\/monday.com\/w\/sidekick\"><strong>monday sidekick<\/strong><\/a><strong> for AI-assisted sorting:<\/strong> monday sidekick is a context-aware assistant that can recommend how to sort a backlog, draft the classification criteria, and answer questions about your boards in plain language. As you scale, Sidekick helps keep the effort balance in view rather than buried in a spreadsheet.<\/li>\n<li><strong>monday agents for high-volume prioritization:<\/strong> For repeatable, high-volume prioritization, monday agents are task-specific AI workers that act inside your boards. The <a href=\"https:\/\/monday.com\/w\/ai-templates\/ai-agents\/sprint-planner-agent\">Sprint Planner<\/a> organizes your backlog and drafts sprint goals around your team&#8217;s capacity, giving you a starting point for what fits in the timebox. The <a href=\"https:\/\/monday.com\/w\/ai-templates\/ai-agents\/dependency-and-risk-mapper\">Dependency and Risk Mapper<\/a> traces dependency chains and flags where a slip could cascade, covering the sequencing gap MoSCoW doesn&#8217;t handle on its own. Agents work alongside your team rather than replacing anyone, so people keep the final call on what&#8217;s a must-have. Every agent runs on mondayDB, one connected data layer spanning marketing, sales, ops, IT, HR, product, and legal, with 200+ integrations and MCP keeping the rest of your stack in sync.<\/li>\n<\/ul>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"2\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"Transform MoSCoW priorities into real progress","content_block":[{"acf_fc_layout":"text","content":"<p>The\u00a0real value of the MoSCoW method isn&#8217;t the four labels; it&#8217;s the clarity they force. When your team agrees what&#8217;s a must-have and what&#8217;s deferred, you protect the deadline and ship the work that actually matters. That shared honesty is what keeps scope creep from swallowing the release.<\/p>\n<p>The next step is keeping those priorities alive as conditions change. Pairing the MoSCoW method with AI-assisted scoring and risk detection lets you re-sort the list the moment reality shifts, instead of once a quarter. On <a href=\"https:\/\/monday.com\/blog\/product\/work-os\/\">a connected work platform<\/a>, your priorities move as fast as your work does.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"3\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<div class=\"accordion faq\" id=\"faq-moscow-method-faqs\">\n  <h2 class=\"accordion__heading section-title text-left\">MoSCoW method FAQs<\/h2>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-1\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What does MoSCoW stand for?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>MoSCoW stands for must-have, should-have, could-have, and won't-have (this time). Each term is a priority category. The lowercase Os are filler letters added only to make the acronym easier to say, so they carry no meaning of their own.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-2\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Who created the MoSCoW method?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>The MoSCoW method was created by software developer Dai Clegg in 1994. He designed it to help teams prioritize requirements during rapid, timeboxed development, and it was later documented in the Dynamic System Development Method (DSDM) handbook.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-3\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Is MoSCoW an Agile technique?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>Yes, MoSCoW is an Agile technique closely tied to the DSDM framework maintained by the Agile Business Consortium. It suits timeboxed delivery because it fixes priorities before a cycle begins, helping Agile teams decide what to include in a sprint or release.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-4\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the disadvantages of the MoSCoW method?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>The main disadvantages of the MoSCoW method are subjectivity and limited ranking. Categorization relies on judgment rather than numbers, so teams can disagree on what counts as a must-have. It also doesn't rank within categories on its own or account for task dependencies.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-5\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What percentage of tasks should be must-have?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-5\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>DSDM guidance recommends keeping must-have requirements to no more than roughly 60% of a timebox's effort. The remaining effort covers should-haves and a contingency pool of about 20% could-haves, which gives the team room to absorb delays without missing the deadline.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-moscow-method-faqs\" href=\"#q-moscow-method-faqs-6\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How does monday AI Workspace support MoSCoW prioritization?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-moscow-method-faqs-6\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-moscow-method-faqs\">\n      <p>monday AI Workspace supports MoSCoW prioritization with priority columns, board views, and dashboards that keep every category visible in real time. Automations update priorities as work changes, while Sidekick and agents help sort backlogs and flag risks, so people keep the final decision.<\/p>\n    <\/div>\n  <\/div>\n  <script type='application\/ld+json'>{\n    \"@context\": \"https:\\\/\\\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What does MoSCoW stand for?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>MoSCoW stands for must-have, should-have, could-have, and won't-have (this time). Each term is a priority category. The lowercase Os are filler letters added only to make the acronym easier to say, so they carry no meaning of their own.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Who created the MoSCoW method?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The MoSCoW method was created by software developer Dai Clegg in 1994. He designed it to help teams prioritize requirements during rapid, timeboxed development, and it was later documented in the Dynamic System Development Method (DSDM) handbook.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Is MoSCoW an Agile technique?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Yes, MoSCoW is an Agile technique closely tied to the DSDM framework maintained by the Agile Business Consortium. It suits timeboxed delivery because it fixes priorities before a cycle begins, helping Agile teams decide what to include in a sprint or release.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are the disadvantages of the MoSCoW method?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The main disadvantages of the MoSCoW method are subjectivity and limited ranking. Categorization relies on judgment rather than numbers, so teams can disagree on what counts as a must-have. It also doesn't rank within categories on its own or account for task dependencies.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What percentage of tasks should be must-have?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>DSDM guidance recommends keeping must-have requirements to no more than roughly 60% of a timebox's effort. The remaining effort covers should-haves and a contingency pool of about 20% could-haves, which gives the team room to absorb delays without missing the deadline.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How does monday AI Workspace support MoSCoW prioritization?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>monday AI Workspace supports MoSCoW prioritization with priority columns, board views, and dashboards that keep every category visible in real time. Automations update priorities as work changes, while Sidekick and agents help sort backlogs and flag risks, so people keep the final decision.<\\\/p>\\n\"\n            }\n        }\n    ]\n}<\/script><\/div>\n\n"}]}]}],"show_sidebar_sticky_banner":false,"disclaimer":"","post_date":"20260926"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>MoSCoW method: categories, steps, and real examples<\/title>\n<meta name=\"description\" content=\"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won&#039;t-have, with clear steps, a matrix example, and best practices.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MoSCoW method: categories, steps, and real examples\" \/>\n<meta property=\"og:description\" content=\"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won&#039;t-have, with clear steps, a matrix example, and best practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/\" \/>\n<meta property=\"og:site_name\" content=\"monday.com Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-25T11:49:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-26T08:16:11+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1344\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Rebecca Noori\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rebecca Noori\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/\"},\"author\":{\"name\":\"Rebecca Noori\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/3f3fef2ad6227357a3948c6473a482d8\"},\"headline\":\"What is the MoSCoW method? A guide to prioritizing what matters\",\"datePublished\":\"2026-01-25T11:49:40+00:00\",\"dateModified\":\"2026-09-26T08:16:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/\"},\"wordCount\":1669,\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/moscow-method-s1_2026-08-30T09-28-09.png\",\"articleSection\":[\"Project management\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/\",\"name\":\"MoSCoW method: categories, steps, and real examples\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/moscow-method-s1_2026-08-30T09-28-09.png\",\"datePublished\":\"2026-01-25T11:49:40+00:00\",\"dateModified\":\"2026-09-26T08:16:11+00:00\",\"description\":\"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won't-have, with clear steps, a matrix example, and best practices.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#primaryimage\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/moscow-method-s1_2026-08-30T09-28-09.png\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/moscow-method-s1_2026-08-30T09-28-09.png\",\"width\":1344,\"height\":768,\"caption\":\"What is the MoSCoW method A guide to prioritizing what matters\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/moscow-prioritization-method\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Project management\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"What is the MoSCoW method? A guide to prioritizing what matters\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/\",\"name\":\"monday.com Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/monday.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\",\"name\":\"monday.com Blog\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/res.cloudinary.com\\\/monday-blogs\\\/fl_lossy,f_auto,q_auto\\\/wp-blog\\\/2020\\\/12\\\/monday.com-logo-1.png\",\"contentUrl\":\"https:\\\/\\\/res.cloudinary.com\\\/monday-blogs\\\/fl_lossy,f_auto,q_auto\\\/wp-blog\\\/2020\\\/12\\\/monday.com-logo-1.png\",\"width\":200,\"height\":200,\"caption\":\"monday.com Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/3f3fef2ad6227357a3948c6473a482d8\",\"name\":\"Rebecca Noori\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g\",\"caption\":\"Rebecca Noori\"},\"description\":\"Rebecca Noori is a seasoned content marketer who writes high-converting articles for SaaS and HR Technology companies like UKG, Deel, Toggl, and Nectar. Her work has also been featured in renowned publications, including Forbes, Business Insider, Entrepreneur, and Yahoo News. With a background in IT support, technical Microsoft certifications, and a degree in English, Rebecca excels at turning complex technical topics into engaging, people-focused narratives her readers love to share.\",\"sameAs\":[\"http:\\\/\\\/www.copywriterandeditor.com\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/rebecca-noori\\\/\"],\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/author\\\/rebeccanoori\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"MoSCoW method: categories, steps, and real examples","description":"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won't-have, with clear steps, a matrix example, and best practices.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/","og_locale":"en_US","og_type":"article","og_title":"MoSCoW method: categories, steps, and real examples","og_description":"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won't-have, with clear steps, a matrix example, and best practices.","og_url":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/","og_site_name":"monday.com Blog","article_published_time":"2026-01-25T11:49:40+00:00","article_modified_time":"2026-09-26T08:16:11+00:00","og_image":[{"width":1344,"height":768,"url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png","type":"image\/png"}],"author":"Rebecca Noori","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rebecca Noori","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#article","isPartOf":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/"},"author":{"name":"Rebecca Noori","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/3f3fef2ad6227357a3948c6473a482d8"},"headline":"What is the MoSCoW method? A guide to prioritizing what matters","datePublished":"2026-01-25T11:49:40+00:00","dateModified":"2026-09-26T08:16:11+00:00","mainEntityOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/"},"wordCount":1669,"publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png","articleSection":["Project management"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/","url":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/","name":"MoSCoW method: categories, steps, and real examples","isPartOf":{"@id":"https:\/\/monday.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#primaryimage"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png","datePublished":"2026-01-25T11:49:40+00:00","dateModified":"2026-09-26T08:16:11+00:00","description":"Learn how the MoSCoW method sorts work into must-have, should-have, could-have, and won't-have, with clear steps, a matrix example, and best practices.","breadcrumb":{"@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#primaryimage","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/01\/moscow-method-s1_2026-08-30T09-28-09.png","width":1344,"height":768,"caption":"What is the MoSCoW method A guide to prioritizing what matters"},{"@type":"BreadcrumbList","@id":"https:\/\/monday.com\/blog\/project-management\/moscow-prioritization-method\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/monday.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Project management","item":"https:\/\/monday.com\/blog\/project-management\/"},{"@type":"ListItem","position":3,"name":"What is the MoSCoW method? A guide to prioritizing what matters"}]},{"@type":"WebSite","@id":"https:\/\/monday.com\/blog\/#website","url":"https:\/\/monday.com\/blog\/","name":"monday.com Blog","description":"","publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/monday.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/monday.com\/blog\/#organization","name":"monday.com Blog","url":"https:\/\/monday.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","contentUrl":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","width":200,"height":200,"caption":"monday.com Blog"},"image":{"@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/3f3fef2ad6227357a3948c6473a482d8","name":"Rebecca Noori","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d64eedbe1d1bd0286197e94bd4d47f76ef501a48b048847f1e106315c98ed42d?s=96&d=mm&r=g","caption":"Rebecca Noori"},"description":"Rebecca Noori is a seasoned content marketer who writes high-converting articles for SaaS and HR Technology companies like UKG, Deel, Toggl, and Nectar. Her work has also been featured in renowned publications, including Forbes, Business Insider, Entrepreneur, and Yahoo News. With a background in IT support, technical Microsoft certifications, and a degree in English, Rebecca excels at turning complex technical topics into engaging, people-focused narratives her readers love to share.","sameAs":["http:\/\/www.copywriterandeditor.com","https:\/\/www.linkedin.com\/in\/rebecca-noori\/"],"url":"https:\/\/monday.com\/blog\/author\/rebeccanoori\/"}]}},"auth_debug":{"user_exists":false,"user_id":0,"user_login":null,"roles":[],"authenticated":false,"get_current_user_id":0},"_links":{"self":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/108380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/users\/219"}],"replies":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/comments?post=108380"}],"version-history":[{"count":35,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/108380\/revisions"}],"predecessor-version":[{"id":364099,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/108380\/revisions\/364099"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media\/364100"}],"wp:attachment":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media?parent=108380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/categories?post=108380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/tags?post=108380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}