Explainer Established Frameworks

MoSCoW โ€” Scope Bucketing

Must / Should / Could / Won't scope bucketing, and where it shows up in your problem template, AI Agent for PM and RADAR.

Generated
November 18, 2026, 3:24 PM MT
Created
November 18, 2026, 3:22 PM MT
Built from
  • wiki/concepts/moscow.md
  • wiki/concepts/problem-definition-template.md

Industry standard

Scope bucketing into Must / Should / Could / Won't have. It answers "given everything scored, what's actually in scope for this release?"

Relative, so it runs on a batch.

Origin

MoSCoW: Established scope technique. Cite it by author when you use it.

4buckets
Batchnot per feature
MVPscoping use

Buckets

MMust haveIn scope for this release
SShould haveImportant, not essential
CCould haveIf there's room
WWon't haveOut of scope this time

How it's used

Question it answersGiven everything scored, what's actually in scope for this release?
ConstraintRelative: it needs the full scored candidate set, so it runs on a batch.

In your frameworks and projects

Your own work, kept separate from the standard above. Your frameworks are the six D's ("Car is IE"), STARTIFY and RADAR.

Problem definition templateThe last section: a Priority / Subfeature / Description / Rationale table that scopes an MVP before Solution Evaluation.
AI Agent for PMThe MoSCoW Agent buckets the batch alongside WSJF ranking; where a bucket and the rank conflict, the draft shows the conflict instead of resolving it.
RADARRADAR's gate step plays the role of MoSCoW's must-haves.