A Fresh, Practical Method of Product Backlog Prioritization cover image
Product Management

A Fresh, Practical Method of Product Backlog Prioritization

Explore an alternative to MoSCoW prioritization for clearer project planning.

Mike Cohn
Oct 12, 2021 • 4 min read
-
Intermediate
Needs Analysis
Problem Statements
Product Requirements
Product Roadmap
Requirements Prioritization

Summary

This resource examines the limitations of the MoSCoW prioritization technique in product development, suggesting an alternative approach of categorizing features into 'Needs, Wants, and Wishes.' The author shares personal experiences and insights on why this method provides clearer guidance for prioritization, especially in agile contexts. Professionals interested in improving their backlog management and prioritization strategies will find this content invaluable. Dive in to discover a more effective way to manage your project priorities.

Takeaways

  • 'Needs, Wants, and Wishes' offers a clearer framework for distinguishing feature priorities.
  • MoSCoW prioritization often leaves 'Could-Have' features unimplemented, suggesting inefficiencies.
  • This alternative approach simplifies stakeholder communication and expectation management.
  • The MSCW acronym stands for: Must have, Should have, Could have, and Will Not have.
  • The MSCW backlog prioritization technique is used to sort out product requirements for a non-agile project.
  • The MSCW prioritization method argues that the Must-have items are the first priority when coming up with the backlog requirements. Whereas the should-have items are included but the product can be launched without some of them, and the could-have items are those that customers desire but the product team deems them of low value.

Suggested Resources