MoSCoW
MoSCoW is a prioritization technique used to classify project features into four categories: 'Must have', 'Should have', 'Could have', and 'Would like but won't get'. This helps teams clarify what is essential for success and what can be deferred due to constraints.
Comment l'animer
- 1
Identify all the features you want to develop within a specific timeframe, such as a Sprint.
- 2
Create a diagram with the four categories: Must have, Should have, Could have, and Would like but won't get.
- 3
Place each feature into the appropriate category.
- 4
Discuss and agree on what constitutes a 'Must have' feature as critical for success.
- 5
Determine what qualifies as 'Should have' and 'Could have' features based on importance.
- 6
Identify the features in the 'Would like but won't get' category that are not feasible.
- 7
Plan actionable tasks based on categorized features.
Conseils
Engage all team members in the prioritization process to ensure diverse perspectives.
Use visual aids like sticky notes to help with categorization and discussions.
Regularly revisit and adjust the priorities as project needs change.
Variantes
The categories can be adjusted to suit the context, such as adding 'Won't have' for clear boundaries.
Contextes d'utilisation
Méthodes associées
Planifiez votre prochain atelier avec l'IA
Workshop Weaver vous aide à combiner des méthodes comme MoSCoW en un agenda complet et minuté en quelques minutes.
Essayer gratuitementMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from SessionLab. Licensed under CC BY-SA 4.0.