journey based on the prioritization methodology proposed by Dai Clegg in 1994
what is it
a journey that aims to define the functionalities or priority requirements, or not, in project management and product development. the name is an acronym formed by the initials of the prioritization categories, added with the letter “o” to make the composition easy to remember, a classification that is divided into: M (must), S (should) , C (could) and W (won’t).
why to use
the MoSCoW methodology is simple and dynamic, allowing an evolutionary and iterative prioritization process. therefore, a resource that was considered disposable or unwanted may one day become mandatory, depending on the type of product, for example.
when to use
the MoSCoW prioritization technique plays a key role in agile methodologies, when time is a fixed resource to be applied to requirements, tasks, services, products and that needs to be optimized.
how to use
the prioritization journey based on the MoSCoW methodology has four points of divergence that must be applied with the team to define each of the categories adapted from the original methodology by Dai Clegg. for each of them, we put together a divergence kit on strateegia.digital with questions to help the team collaboratively define the decisions needed for the project.
each block of Dai Clegg’s original methodology was converted into a divergence kit, generating the four kits in the list below:
- must have
- should have
- could have
- won’t have