Scrum is founded on empiricism and lean thinking. Empiricism means decisions are based on what is known through transparency, inspection, and adaptation.

Scrum Foundations: Framework, Empiricism, and Scrum Values — Professional Scrum Master I (PSM I) Complete Exam-Ready Mastery Course

Q: During the Daily Scrum, team members mechanically answer the three classic questions but do not look at the Sprint Goal or adjust their plan. Impediments are rarely raised because people fear being blamed. Which combination best describes what is missing?

Adaptation and courage. The event lacks **adaptation** (they do not adjust the plan based on information) and **courage** (they fear raising impediments). Transparency and inspection are present but shallow; the core missing elements are adaptation and the value of courage.

Scrum Foundations: Why This Matters for PSM I

Module Focus

In this module you connect three pillars of your PSM I prep: the Scrum framework, empiricism, and Scrum values. These ideas show up in many exam questions, often in subtle ways.

Current Reference

As of now (late May 2026), the Scrum Guide 2020 is still the current official description of Scrum. When a question says "according to Scrum", assume it refers to this 2020 version.

Two Canonical Sentences

Memorize these: 1) Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. 2) Scrum is founded on empiricism and lean thinking.

Learning Path

We will connect Scrum to complex work, unpack empiricism, overview the framework, then go deep into the five Scrum values with behavior-focused examples and exam traps.

Scrum in Complex, Uncertain Work

Why Scrum Exists

Scrum was created for complex work where cause and effect are not obvious and plans quickly become outdated. Software is classic, but the same pattern appears in AI, biotech, and digital products.

Complex vs Predictable

In complex domains you cannot fully design the solution upfront. Requirements change, tech and markets shift, and surprises are normal rather than exceptional.

Limits of Predictive Planning

Traditional predictive approaches assume stability and fixed scope, cost, schedule. They fit complicated domains better than truly complex, fast-changing environments.

Scrum’s Response

Scrum accepts that you learn as you go. It uses short Sprints, frequent inspection of product and process, and adaptation of plans based on what you learn.

Exam Angle

In PSM I, Scrum-aligned answers emphasize adaptation to change, frequent feedback, and delivering usable Increments over strictly following an upfront plan.

Canonical Definition of Scrum

Official Definition

Know this verbatim: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Lightweight Framework

Scrum is lightweight: a minimal set of roles, events, and artifacts. It is a framework, not a detailed methodology telling you how to do every task.

Value and Adaptation

Scrum helps people, teams, and organizations generate value. Value is the outcome. Solutions are adaptive, evolving as you learn rather than fixed upfront.

Optimized for Complexity

Scrum is designed for complex problems, where requirements and solutions emerge over time. It is not optimized for simple, repeatable work.

Exam Traps

Watch for options calling Scrum a methodology or focusing on control and documentation over value and adaptation. Prefer answers aligned with the official definition.

Empiricism and Lean Thinking

Foundations

The Scrum Guide states: Scrum is founded on empiricism and lean thinking. This sentence is a common exam target, so remember it exactly.

Empiricism

Empiricism means making decisions based on what is known: observed evidence, not speculation. In Scrum you learn by doing and inspecting real results.

Lean Thinking

Lean thinking focuses on reducing waste, maximizing customer value, and optimizing flow. Work that does not contribute to value is minimized.

Combined Effect

Together they mean: build small Increments, inspect them, adapt based on evidence, and avoid heavy upfront prediction or unnecessary work.

Exam Lens

When you see rigid plans, long cycles, or heavy analysis without delivery, the Scrum-aligned answer is to shorten feedback loops and inspect real Increments more often.

The Three Pillars of Empiricism

Three Pillars

Empiricism in Scrum stands on three pillars: transparency, inspection, and adaptation. These show up across roles, events, and artifacts.

Transparency

Transparency means work and progress are visible and understandable. Clear Product and Sprint Backlogs and a shared Definition of Done are key examples.

Inspection

Inspection is the frequent, purposeful look at artifacts and progress toward goals, such as reviewing the Increment at Sprint Review or progress at Daily Scrum.

Adaptation

Adaptation means changing the product or the way of working when inspection shows things are off track. You adjust as soon as possible.

Spotting Missing Pillars

Hidden work or unclear Done points to missing transparency. Status-only events suggest weak inspection. Seeing problems but not changing behavior shows missing adaptation.

Scrum Framework Overview: Roles, Events, Artifacts

Scrum Team

The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal. It includes a Product Owner, Scrum Master, and Developers.

Accountabilities

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.

Developers

Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. They are not limited to coders; any makers of the Increment.

Sprints

Sprints are the heartbeat of Scrum, where ideas are turned into value. Each Sprint is one month or less and contains all other Scrum events.

Artifacts

The Product Backlog is an emergent, ordered list of what is needed to improve the product. The Sprint Backlog holds the Sprint Goal, selected items, and plan. An Increment is a concrete stepping stone toward the Product Goal.

Goals and Quality: Product Goal, Sprint Goal, Definition of Done

Product Goal

The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. It gives long-term direction.

Sprint Goal

The Sprint Goal is the single objective for the Sprint. It aligns everyone on purpose while allowing flexibility in the exact work.

Definition of Done

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It makes quality transparent.

Common Confusions

Do not treat the Sprint Goal as a list of items. Do not confuse Product Goal (long-term) with Sprint Goal (per Sprint). The Definition of Done applies to the Increment as a whole.

Values Link

These concepts connect to values: Commitment to goals and DoD, Focus on the Sprint Goal, and Openness about what is truly done.

Scrum Values: The Human Side of the Framework

Five Scrum Values

Scrum relies on five values: commitment, focus, openness, respect, and courage. These describe the behaviors that make the framework work in practice.

Values Support Empiricism

Without openness and courage, transparency is weak. Without commitment and focus, inspection is shallow. Without respect, adaptation becomes blame and problems get hidden.

Commitment and Focus

Commitment means personally committing to the Scrum Team’s goals. Focus means concentrating on the work of the Sprint and the team’s goals, minimizing distractions.

Openness and Respect

Openness is being transparent about work and challenges. Respect is treating others as capable, independent professionals, even when you disagree.

Courage and Exam Link

Courage is doing the right thing and raising tough issues. On PSM I, you’ll map behaviors in scenarios to the value that is present or missing.

Scrum Values in Action: Behavioral Scenarios

Scenario 1: Quality

Developers admit they cut corners and the Increment does not meet the Definition of Done. They choose not to release and commit to fixing it next Sprint. Values: courage, openness, commitment.

Scenario 2: Hidden Work

A Developer does side tasks for a manager that are not in the Sprint Backlog, delaying Sprint work. Missing values: openness, focus, and commitment to the Sprint Goal.

Scenario 3: Disagreement

Product Owner and Developers disagree about a technical item but discuss calmly, listen, and adjust backlog ordering after understanding risks. Values: respect, openness, courage.

Exam Strategy

In questions where multiple values seem relevant, pick the one most central to the behavior: hidden work → openness/focus; fear to speak → courage; blaming → lack of respect.

Thought Exercise: Mapping Events to Empiricism

Exercise Instructions

For each Scrum event, ask: 1) What becomes transparent? 2) What is inspected? 3) What can be adapted as a result? Pause and think before reading hints.

Sprint Planning

Transparency: Product Goal, capacity, backlog items. Inspection: backlog and past performance. Adaptation: Sprint Goal, selected items, and plan for the Sprint.

Daily Scrum

Transparency: current progress toward the Sprint Goal. Inspection: progress, risks, impediments. Adaptation: the plan for the next 24 hours.

Sprint Review

Transparency: the Increment and current Product Backlog. Inspection: product value and progress toward the Product Goal. Adaptation: Product Backlog ordering and ideas.

Sprint Retrospective

Transparency: how we worked, processes, tools. Inspection: team dynamics and practices. Adaptation: concrete improvements and possible DoD updates for the next Sprint.

Quiz 1: Definitions and Foundations

Test your recall of key Scrum foundations. Focus on exact wording and concepts.

Which option best matches the official definition of Scrum from the Scrum Guide 2020?

Scrum is an agile methodology that helps software teams deliver projects on time and on budget through iterative planning and continuous improvement.
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Scrum is a project management process that divides work into Sprints to ensure transparency, inspection, and adaptation.
Scrum is a prescriptive set of practices that guarantees successful delivery of complex products when followed correctly.

Show Answer

Answer: B) Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

The canonical definition is: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. The other options distort it by calling Scrum a methodology, process, or prescriptive set of practices, or by narrowing it to projects or software only.

Quiz 2: Empiricism and Values in Scenarios

Apply what you learned about empiricism and Scrum values to a scenario.

During the Daily Scrum, team members mechanically answer the three classic questions but do not look at the Sprint Goal or adjust their plan. Impediments are rarely raised because people fear being blamed. Which combination best describes what is missing?

Transparency and focus
Inspection and commitment
Adaptation and courage
Respect and openness