A technique to manage requirements by categorizing them into four priority groups.
Critical to the current delivery timebox. Without these, the project fails.
Important but not vital. Can be painful to leave out, but the solution is still viable.
Desirable but not necessary. Include these only if time and resources permit.
Agreed not to have this time. Can be reconsidered for a future release.
Gather all potential features, requests, and ideas into a single backlog.
Be clear about the deadline (e.g., "For the MVP launch in 3 months").
As a team (including stakeholders), assign each feature to a category. Debate is healthy here.
Ensure "Must Haves" don't take up 100% of your capacity. Aim for 60% Musts to allow buffer for Shoulds.