The MoSCoW method (also known as MoSCoW prioritization or MoSCoW analysis) is a prioritization technique to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement. The term MoSCoW itself is an acronym derived from the first letter of each of four prioritization categories as shown in the Figure below:
Must (Mo) – The requirements that are critical and must be applied to a product as a matter of priority. Even if one of them is not taken into account, the release is considered to be unfulfilled.
Should (S) – Requirements important but not critical for the release. Such requirements are not very sensitive to time.
Could (Co) – Desirable but not mandatory requirements for your release. These are usually low-cost improvements for the product.
Would (W) – These are considered the least critical or may not correspond to the product strategy at all. They can be ignored and be revised for future releases.
Note That
The interstitial characters “o” added to make the word “MoSCoW” pronounceable. While the characters “o” are usually in lower-case to indicate that they do not stand for anything, through the all-capitals MOSCOW is also used.
MoSCoW is often used with timeboxing, where a deadline is fixed so that the focus must be on the most important requirements, and as such is a technique commonly used in agile software development approaches such as Scrum and DSDM.
Best Scrum Software Every Project Needs
A powerful scrum software that supports scrum project management. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.
Take a human body as an hypothetic example:
The Product Owner is responsible for getting the Product Backlog ready and prioritizing the items in the Product Backlog. Prioritization is one of the most important aspects of any form of development work because choosing the right thing to do allows you to maximize the value delivered in a Sprint. The Product Backlog items should be ordered in such a way that the requirements with maximum business value would be completed first and empowers a team to move in a uniform direction towards a common goal.
When performing the prioritization of your product backlog items at the Sprint planning session, here is a list criteria to be considered for your decisions.
| About Visual Paradigm |
 Visual Paradigm help organizations stay competitive and responsive to change faster and better in today’s fast changing environment. Our award-winning products are trusted by over 320,000 users in companies ranging from small business, consultants, to blue chip organizations, universities and government units across the globe. It enables organizations to improve business and IT agility and foster innovation through popular open standards and process frameworks.Visual Paradigm, a killer Agile feature in 2018, introduced Scrum Process Canvas for automating the way a Scrum team to create, manage and deploy software application that empowers the team to continuously improve their performance at unprecedented speed and scale.
Manage the Entire Scrum Process in One Page
|
