They can’t have it all right? So the next time you’re sorting through a long, long list of requirements with a group of stakeholders, consider using the MoSCoW method. 

The MoSCoW Method is a prioritisation technique based on whether requirements are ‘must have’, ‘should have’, ‘could have’, or ‘won’t have’ over a defined time period. 

ENGAGING STAKEHOLDERS.

It’s a simple technique that can be easily understood by stakeholders, helping product teams and stakeholders to gain a shared agreement on priority requirements. It can be used to help define scope for a project, identify goals for an Agile Scrum sprint, or to evaluate tenders for a new system or platform.

CATEGORIES IN MORE DETAIL. 

The categories are as follows:  

• Must have: mandatory features that will be prioritised. 
• Should have: great to have features but not critical in this build. They can be seen as important, not urgent and are high contenders to be ‘must’ in the next iteration.  
• Could have: non-essential additions that will add value but their absence will not have a cost. 
• Won’t have: lowest importance, potentially on a road map but not considered for the iteration.

IN YOUR LATTICEWORK.

The MoSCoW Method is a useful prioritisation framework when gathering a range of requirements for a product or project. Alternative prioritisation methods include the RICE Score, Impact Effort Matrix and Kano Method. Use it as part of Agile Methodology sprints, including to define and deliver Minimum Viable Products.