MoSCoW Prioritization

MoSCoW prioritization method poster. MoSCoW acronym provides a solution on how to prioritize the work based on the importance of single items.
Read more

MoSCoW Prioritization

MoSCoW prioritization method is a popular method for prioritizing items in your product backlog.

Must have

Minimum Usable SubseT (MUST) of requirements without which there is no value in delivering anything. Delivery without any of these requirements missing is considered a failure.

Should have

Should have requirements are important but not vital. These may be as important as “Must have” but are not so critical (e.g. time). The amout of work can be considered.

Could have

These requirements are also called “nice to have”. Delivered if everything goes smooth else when there are any problems requirements of this type are the first to be dropped.

Won’t have this time

The least critical requirements or not appropriate at the time. Will not be delivered in this timeframe. Can be recorded in a prioritized requirements list to clarify the context

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.