MoSCoW technique
The MoSCoW technique prioritizes requirements as must-have, should-have, could-have, or will-not-have.
"Looks Good to Me"
A MoSCoW comment is a code-review comment classified using must-have, should-have, could-have, or will-not-have priority categories.
- How it is used
- Classifies code-review feedback so authors can prioritize changes and reviewers can signal which comments require action.
- How deep it goes
- Defines four categories and formatting, then notes that blurred boundaries can create arguments about labels instead of suggestions.
- Examples
- Uses import correction, variable renaming, regional product reporting, and loop preference as formatted review comments.
- What you can do after
- Apply it via MoSCoW prefixes to make code-review obligations and optional suggestions explicit.
Think Like a Software Engineering Manager
The MoSCoW technique classifies requirements as must-have, should-have, could-have, or will-not-have to support prioritization.
- How it is used
- Supports project and feature stack ranking during new-product launches or existing-feature enhancements.
- How deep it goes
- Defines four priority categories and gives examples, but stops short of prescribing a detailed scoring process.
- Examples
- Uses security, performance, authentication, comments, later iterations, and Project Accessible to illustrate priority levels.
- What you can do after
- Evaluate and rank requirements for launches or enhancements while aligning stakeholders around business priorities.
Read how Think Like a Software Engineering Manager explains MoSCoW technique →
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.