People Interact

Blog about people-centered design by Lisa Chow and Sandra Sajonas.

Tag Archives: requirements

Monthly Method Spotlight: MoSCoW Prioritization

MoSCoW Prioritization

What & Why:  There can be a lot of features/requirements when it comes to project ideas and projects, also many with short timelines and quick turnaround times. How do you prioritize them? One way to prioritize when managing projects is to use the MoSCow method.

M – MUST HAVE:
Features/Requirements that are non-negotiable for the success of the project.

S – SHOULD HAVE:
High-priority requirements/features that are not critical to launch but are considered important and of a high value.

C – COULD HAVE:
Features/requirements that are desirable but not necessary. May be removed or pushed to future stage of development if project completion timeline is at risk.

W – WOULD LIKE TO HAVE BUT WON’T HAVE (AT THIS TIME): Features/requirements that will not be implemented in a current release but may be included in a future stage of development. Such requirements usually do not affect the project success.

priority-scrabble

How: Request input from your project team and stakeholders using the method. Use a combination of other methods such as dot-voting. This method can also be used in your personal life; anything from making a major purchase like a house or a car (what features are a must have, etc.) to cooking a meal (what ingredients are a must have, what can be skipped, etc.)

We cover the MoSCoW method and other project management methods in our getting started in project management workshop for librarians

Interested in using/applying these methods in your work? Contact us for information.

Advertisements