Use this category only when the content is materially about the Scrum framework.

Definition: Scrum is a lightweight framework for teams delivering usable product increments through empirical inspection, adaptation, and time-boxed Sprints. It is defined by specific accountabilities, events, artefacts, and commitments such as Product Owner, Scrum Master, Sprint Planning, Product Backlog, Sprint Goal, and Definition of Done.

Must have:

• Explicit discussion of Scrum as a framework, not just general agile work or project management
• Scrum accountabilities such as Scrum Team, Product Owner, Developers, or Scrum Master
• Scrum events such as Sprint, Sprint Planning, Daily Scrum, Sprint Review, or Sprint Retrospective
• Scrum artefacts or commitments such as Product Backlog, Increment, Product Goal, Sprint Goal, or Definition of Done
• Empiricism through transparency, inspection, and adaptation, or iterative and incremental delivery of usable increments

Strong fit:

• Primary: Scrum is the main subject and at least two Must have items are discussed.
• Secondary: Scrum is a substantial supporting theme and at least one Must have item is discussed.

Weak fit:

• Tertiary: Scrum is mentioned or adjacent, but the content is mostly about agile, DevOps, product management, software delivery, or team collaboration.
• Ignored: Scrum is absent, only implied, or supported only by generic language about iteration, planning, teamwork, value delivery, or continuous improvement.

Exclude:

• Agile methodology in general when Scrum roles, events, or artefacts are not discussed
• Kanban, Lean, DevOps, SAFe, or generic project management practices unless explicitly framed through Scrum
• Product ownership, backlog management, sprint planning, or retrospectives discussed outside Scrum
• Rugby scrums or sports uses of the term
• Generic terms such as agile, sprint, team, collaboration, planning, delivery, value, or improvement are insufficient on their own