Description
A tool that allows us to establish priorities in the functionalities that our solution should have in order to be a success. Tool that allows to select the solutions to be developed before starting to build them by functionalities. Tool that allows us to establish the most important needs of the users. Tool that allows to agree on the decision making among stakeholders.
What for?
Prioritise the most valuable functionalities or features within the prioritised solution to establish levels of importance within them. Allows to define which are a Must to develop the key value of our solution and determine those that are not so relevant but could complement it
Step by step
- Write in the first column, of MUST HAVE, the functionalities that must be in the final version of the product
- Write in the second column, in SHOULD HAVE, the functionalities with the highest priority, the ones that should be
- Write in the third column of COULD HAVE those features that are desirable but not necessary
- Finally, write in the column of WON'T HAVE the functionalities discarded for the moment but that can be taken into account in the future
Tips for use
- Define with the team and client what each of the MoSCoW categories means for the specific project and business challenge
- Use the percentage of effort as a guide to define the amount of functionalities or solutions that you can assume as a team in a limited time with a concrete working capacity
IMPORTANT: this tool can help you prioritise a Product Backlog so that you know what you need to attack most urgently and what you can leave for next work sprints or iterations
Finance sector project, by Kassandra Martínez
Download tool
