It often happens that a project is hindered by too many wishes from the user organization. However, a development strategy that provides feedback to the customer can prevent over-demanding the development organization. DSDM counteracts this by dividing the functional requirements and wishes into a number of categories in which the priority is indicated for each functionality.

DSDM uses the MoSCoW rules to determine the priorities for requirements and wishes.

MoSCoW stands for:

• Must-have: This category has the highest priority, is guaranteed to be delivered, and counts as the engine of the information system.
• Should-have: A necessary requirement where a (temporary) workaround is possible.
• Could-have: A requirement with a clear added value, but without it there is still a usable system.
• Would-have (or want to have but won't have this time around): This requirement can be missed, although it does not mean that it is not relevant; in the next increment, it can be a must-have.

Nowadays, DSDM is not extensively used. The last decade has seen other methods gain a lot more popularity, especially Agile methods such as Scrum, which we will discuss next.