Within software development, the chunk of work is estimated in time and effort. Often the work has to be prioritized, in order to be able to start with the right piece of work at right time.
Prioritization and ordering of work is a popular topic. Methods vary in complexity and usability. Moscow is however one of the simplies most stright forward methodologies to use.
The o’s does not have any purpose, other than being a word that “suck” better to long term memory. Based on the MoSCoW, product owner or corresponding are able to “communicate” with what priority to pick items from the backlog.<< Back to list all models