Phase 3 · Requirements Analysis & Documentation
TopicsRequirements Prioritization (MoSCoW)
Part of the Business Analyst Roadmap.
Summary
A framework sorting requirements into Must have, Should have, Could have, and Won't have (this time) — helping teams focus on what's truly essential when scope, time, or budget is constrained.
How to Learn This
- 1Sort a list of 8-10 hypothetical requirements using MoSCoW.
- 2Learn why 'Must have' should be a genuinely small, non-negotiable list, not most of the items.
- 3Practice defending a prioritization decision against stakeholder pushback.
More topics in Requirements Analysis & Documentation
Functional vs Non-Functional RequirementsBusiness Requirements Document (BRD)Functional Requirements Document (FRD)User Stories & Acceptance CriteriaUse Cases & Use Case DiagramsRequirements Traceability Matrix (RTM)Writing Clear, Testable RequirementsRequirements Validation & Sign-OffManaging Requirement Changes
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.