2.1 What Scrum Is (and Is Not)

Why This Matters On The Exam

Roughly 60% of the Professional Scrum Master I (PSM I) assessment falls under the focus area Understanding and Applying the Scrum Framework, and almost every distractor in that area exploits a single misconception: that Scrum is a detailed process you follow step by step. org's PSM I exam — 80 questions, 60 minutes, an 85% (68 of 80) passing score, drawn directly from the 2020 Scrum Guide — rewards candidates who can quote the Guide's own framing rather than paraphrase a workplace habit.

If you internalize the precise definition in this section, a large block of questions becomes mechanical: you recognize the Guide-aligned option and reject every distractor that smuggles in a 'methodology' assumption.

The trap is that most candidates have lived a flavor of Scrum at work that bolted on extra meetings, mandatory documentation, or a manager who assigns tasks. The exam tests the framework as written, not as commonly practiced. Train yourself to answer 'What does the 2020 Scrum Guide say?' — not 'What did my last team do?'

The Official Definition

The 2020 Scrum Guide states that Scrum is "a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems." Four phrases carry weight:

• Lightweight — Scrum deliberately specifies very little. The entire Guide is roughly thirteen pages and faster to read than most onboarding documents.
• Framework — not a process, technique, or methodology. Scrum is a container; teams employ many practices inside it.
• Generate value — the point of Scrum is value, not activity, output, or velocity for its own sake.
• Adaptive solutions for complex problems — Scrum targets work where requirements and solutions emerge, not predictable assembly-line work that can be fully specified in advance.

Framework, Not Methodology

This distinction is the single most tested idea in this section. The Scrum Guide says the framework is purposefully incomplete, "only defining the parts required to implement Scrum theory." It also notes that "various processes, techniques and methods can be employed within the framework" and that "Scrum wraps around existing practices or renders them unnecessary. Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made."

Practical implications the exam checks:

• Scrum does not tell you how to write code, estimate, slice work, or design. It defines three accountabilities, five events, and three artifacts, then leaves engineering and management practices to the team.
• Adding practices — a Definition of Ready, story points, planning poker, a particular Daily Scrum format, a burndown chart — is allowed within Scrum, but those practices are not themselves part of Scrum.
• 'ScrumBut' reasoning ('we do Scrum, but we skipped the Retrospective because we were busy') is a red flag the exam wants you to reject.

A classic distractor frames Scrum as 'a complete software development methodology' or 'a project-management process that replaces all organizational processes.' Both contradict the Guide: Scrum is lightweight, incomplete, and domain-agnostic — it is used for product, research, marketing, hardware, and more, not just software.

Immutability: There Is No 'Partial Scrum'

The Scrum Guide is blunt: "The Scrum framework, as outlined herein, is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices."

Read that carefully — immutability does not forbid adding practices around Scrum; it forbids removing the defined parts and still calling it Scrum. The exam frequently presents a team that drops the Sprint Retrospective, lets a manager assign tasks to Developers, runs Sprints with no Sprint Goal, or skips the Sprint Review, then asks whether they are 'doing Scrum.' The Guide-aligned answer is no — the result may still produce some value, but it is not Scrum.

Simple To Understand, Difficult To Master

The Guide closes its purpose section with: "Scrum is simple. Try it as is and determine if its philosophy, theory, and structure help to achieve goals and create value. The Scrum framework is purposefully incomplete... Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions." The rules fit on a few pages, yet mastery is hard because Scrum is engineered to make impediments visible. It does not fix poor product decisions, weak engineering quality, or a low-trust culture; it exposes them so people can act.

Memorize this framing. Questions often contrast 'Scrum solves the problem' (wrong) with 'Scrum makes the problem visible so the team can inspect and adapt' (right). When an executive complains that adopting Scrum revealed more problems than before, the Guide-aligned reading is that this is the framework working as designed — surfacing reality is the prerequisite for transparency, inspection, and adaptation.