skip to Main Content

C — could. This category includes requirements that have a much lower impact if excluded from the project. As a result, perhaps requirements are often the first to be deprioritized – must-have requirements and requirements should always take precedence. Placing initiatives in the “non-have” category is one way to prevent creeping scope development. When initiatives fall into this category, the team knows that they should not be a priority for that particular period. Some initiatives in the “will not” group will be prioritized in the future, while others are unlikely to occur at all. Some teams decide to differentiate them by creating a subcategory within this group. The advantage of the MoSCoW method is that it can be applied to a variety of situations, both in a personal and professional context. For example, an individual could use the method to prioritize their workload for the week, or a team could use it to identify tasks that need to be completed first to meet an impending deadline. In general, the MoSCoW method is most useful when a person or team is faced with a large number of tasks and needs help deciding which one to focus on first. If you`re starting a project and you`re not sure which to prioritize, you can get your team together and use the MoSCoW method as a discussion tool. For example, if a team has too many potential epics (i.e. High-level stories) for the next version of their product, they could use the MoSCoW method to select which epics should have, which ones should have, etc.; The minimum viable product (or MVP) would be all epics marked as Must Have.

[4] Often, a team will find that even after identifying their MVP, they have too much work to do for their expected ability. In such cases, the team could then use the MoSCoW method to select which functions (or stories, if it is the subset of epics in their organization) are “indispensable”, “should have”, etc. the minimum marketable characteristics (or MMFs) would all be marked as indispensable. [5] If there is sufficient capability after selecting the MVP or MMF, the team may consider including targets and even elements. [6] Another important idea about how the MoSCoW technique works is that it is only effective if you follow it. This means that once an initiative has been placed in a category, the entire team must stick to that decision. Many MoSCoW rookie teams agree that an initiative should have been launched, but instead take the next step because they feel better or more familiar. W — I won`t have it. The latter category includes all requirements that have been identified as non-priority for the duration of the project. Assigning items to the “will not” category helps to place greater emphasis on the requirements of the other three categories while setting realistic expectations for what will not be included in a final product.

In addition, this category is advantageous to avoid creeping scope – or the tendency of product or project requirements to exceed the expected level during development. To make sure you`re putting every initiative in the right area – must, should have, could or won`t – your team needs context. Sometimes the letters M, S, C and W are not enough and we may also need a UM (Urgent Must) sign. Unified messages are the most important elements, such as fixes, bug fixes, and fixes that block the work of the entire team. In our experience, we recommend correcting these tasks as soon as possible, as they hinder the productive work of the team. Therefore, if you designate a task as Unified Messaging, you must skip all other tasks until the UM task is resolved. In normal situations, your error monitoring system should not have Unified Messaging. Cross-functional teams can also be constrained by other business priorities. The team wants to make progress on a new product release, but executives have set tight deadlines for other releases within the same timeframe.

In this case, the team can use MoSCoW to determine which aspects of the desired version are essential and bring everything else back temporarily. You can also find this type of requirement under the name “wannabe” or “want-to-have”, but these variations are not recognized by the wiki. However, regardless of the name chosen, these requirements set the lowest priority for tasks that are not achievable with a certain budget and time frame. Not wanting to have does not mean a complete rejection of something. It provides for resettlement under favourable conditions in the future. It is precisely the work that is a priority. Priorities are established before work begins, and most of these priority-setting activities take place during foundations. However, priorities should be constantly reviewed once the work is completed.

What Viewers Are Saying...

Back To Top