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.
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
| M | Must have | In scope for this release |
| S | Should have | Important, not essential |
| C | Could have | If there's room |
| W | Won't have | Out of scope this time |
How it's used
| Question it answers | Given everything scored, what's actually in scope for this release? |
| Constraint | Relative: 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 template | The last section: a Priority / Subfeature / Description / Rationale table that scopes an MVP before Solution Evaluation. |
| AI Agent for PM | The MoSCoW Agent buckets the batch alongside WSJF ranking; where a bucket and the rank conflict, the draft shows the conflict instead of resolving it. |
| RADAR | RADAR's gate step plays the role of MoSCoW's must-haves. |