3-4 minutes<\/p>\n
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 anacronym derived from the first letter of each of four prioritization categories as shown in the Figure below:<\/p>\n
Must (Mo) \u2013 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.<\/p>\n
Should (S) \u2013 Requirements important but not critical for the release. Such requirements are not very sensitive to time.<\/p>\n
Could (Co) \u2013 Desirable but not mandatory requirements for your release. These are usually low-cost improvements for the product.<\/p>\n
Would (W) \u2013 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.<\/p>\n
The interstitial characters \u201co\u201d added to make the word \u201cMoSCoW\u201d pronounceable. While the characters \u201co\u201d are usually in lower-case to indicate that they do not stand for anything, through the all-capitals MOSCOW is also used.<\/p>\n
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.<\/p>\n
Take a human body as a hypothetic example:<\/p>\n
Must \u2013 a heart is \u201cmust\u201d. Without it, there is no live organism. What is a must in your application?<\/p>\n
Should \u2013 a hand is \u201cshould\u201d. Without it is hard. But you can survive even without hand. Well, in most cases.<\/p>\n
Could \u2013 hair is \u201ccould\u201d. It is fine to have them, you even look nicer, but you will survive without them<\/p>\n
Won\u2019t \u2013 unnecessary waste. Btw, is there anything \u201cwon\u2019t\u201d in a body? (Probably, it might be your appendix?)<\/p>\n
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.<\/p>\n","protected":false},"excerpt":{"rendered":"