{
  "id": "methodology:MoSCoW-prioritization",
  "_kind": "Methodology",
  "_file": "domain/methodologies/methodologies-expanded.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "MoSCoW Prioritization",
    "description": "A prioritization technique that classifies requirements into four categories:\nMust have (non-negotiable for the release), Should have (important but not\ncritical), Could have (desirable if time permits), and Won't have (explicitly\nout of scope this time). Used within timeboxed iterations to manage scope\nand set clear stakeholder expectations about delivery guarantees.\n",
    "methodologyKind": "prioritization",
    "origin": "Dai Clegg",
    "yearIntroduced": "1994"
  },
  "outgoingEdges": [
    {
      "from": "methodology:MoSCoW-prioritization",
      "to": "domain:project-management",
      "kind": "applies_to"
    },
    {
      "from": "methodology:MoSCoW-prioritization",
      "to": "domain:software-engineering",
      "kind": "applies_to"
    }
  ],
  "incomingEdges": []
}