MoSCoW Technique

Owned by Elliott, Stephen (TC TC) (Unlicensed)
Apr 06, 2023
1 min read

Categorizing the needs:  

Assigning requirements to the should-have and could-have categories does not mean the team won't deliver the element; it just reveals that it is not necessary for completion and, therefore, is not guaranteed.  

  

Must Have  

  • There is no point completing the project by its target deadline without this requirement.  

  • The final product or software does not deliver an effective solution without this requirement.  

Should Have  

  • If the final product doesn't include should-have requirements, then the product still functions. However, if it does include should-have elements, they greatly increase the value of the product  

Could Have  

  • Could-have requirements are often the first ones teams deprioritize, An example of a could-have is a desirable but unimportant element.  

Would Have  

All the requirements the team recognizes as not a priority for the project's time frame, this category is beneficial in preventing scope creep