MoSCoW

MoSCoW is a method that allows the team to prioritize the different features that they will work on. Features are then categorized into “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”.

MoSCoW

2 HOURS - 4 HOURS

back

TASKS

1. List all the features that you want to develop within a specific time frame (for example a Sprint).
2. Make a diagram that has the four different categories “Must have”, “Should have”, “Could have”, or “Would like but won’t get”. Classify the features within the four categories.
3. “Must have” are features that are critical and need to be implemented to have a successful product.
4. “Should have” are features that are important but are not critical, they can be done in a different way.
5. “Could have” are features that would be nice to have, but won’t make a significant change in the user experience.
6. “Would like but won’t get” are features that are too difficult to implement.
7. Once the different features have been rated, plan accordingly by defining tasks.

WHEN

At the beginning of a timeslot (for example during Sprint planning) and when planning is needed.

WHY

Allows to make a clear hierarchy of what needs to be implemented, and what is not feasible to include within the current constraints.

NOTE!

Be realistic about what is actually needed and what is feasible to do.

OUTPUT

A work plan that can be distributed among the design team.

Next

Follow and track the plan, make sure to communicate it clearly to the team.

MoSCoW

2 HOURS - 4 HOURS

MoSCoW is a method that allows the team to prioritize the different features that they will work on. Features are then categorized into “Must have”, “Should have”, “Could have”, or “Would like but won‘t get”.

TASKS

1. List all the features that you want to develop within a specific time frame (for example a Sprint).
2. Make a diagram that has the four different categories “Must have”, “Should have”, “Could have”, or “Would like but won’t get”. Classify the features within the four categories.
3. “Must have” are features that are critical and need to be implemented to have a successful product.
4. “Should have” are features that are important but are not critical, they can be done in a different way.
5. “Could have” are features that would be nice to have, but won’t make a significant change in the user experience.
6. “Would like but won’t get” are features that are too difficult to implement.
7. Once the different features have been rated, plan accordingly by defining tasks.

WHEN

At the beginning of a timeslot (for example during Sprint planning) and when planning is needed.

WHY

Allows to make a clear hierarchy of what needs to be implemented, and what is not feasible to include within the current constraints.

NOTE!

Be realistic about what is actually needed and what is feasible to do.

OUTPUT

A work plan that can be distributed among the design team.

Next

Follow and track the plan, make sure to communicate it clearly to the team.