Why Does the Scrum Guide Start With Empiricism? Because Scrum Is Incomplete Without It
The 2020 Scrum Guide opens by stating that Scrum is founded on empiricism and lean thinking. Then it defines empiricism as asserting that knowledge comes from experience and making decisions based on what is observed. This isn't philosophical window-dressing—it's the architecture that makes every other Scrum element coherent. If you don't understand why empiricism is the foundation, the events and artifacts feel like arbitrary ceremonies rather than a coherent system.
What Is Empiricism and Why Does Scrum Rely on It?
Empiricism is the idea that you learn by doing, observing, and adjusting—not by planning extensively in advance and executing the plan. Complex product development is inherently unpredictable. You can't know at the start of a six-month project exactly what customers will need in month four, what technical obstacles will emerge in month five, or what the market will look like at delivery. Any plan you build upfront will be partially wrong.
Traditional project management tries to solve this by planning more carefully, adding checkpoints, and managing risk. Scrum takes a different approach: create short feedback loops (Sprints) that deliver real working product, inspect what you've learned, and adapt your plan accordingly. This is empirical process control—make a small bet, observe the result, adjust the next bet.
The Scrum Alliance CSM exam tests whether you understand this philosophy deeply enough to apply it in scenarios. A question might describe a team that's following all the Scrum events but still delivering software that doesn't match customer needs—and ask what's wrong. The answer often connects back to a failure of empiricism: the team isn't genuinely inspecting and adapting based on real feedback.
The Three Pillars: Transparency, Inspection, and Adaptation
Scrum's implementation of empiricism rests on three pillars. These are the specific mechanisms through which empirical process control operates in the framework.
Transparency means that significant aspects of the process must be visible to those performing the work and those receiving it. Without transparency, inspection is impossible—you can't inspect what you can't see. The Product Backlog, Sprint Backlog, and Increment are all artifacts of transparency. The Definition of Done is a transparency mechanism. When a team's Definition of Done is weak or inconsistently applied, transparency breaks down: stakeholders think work is "done" when it isn't really done. This is one of the most common Scrum failures in real organizations.
Inspection means that Scrum users must frequently inspect Scrum artifacts and progress toward agreed-upon goals to detect potentially undesirable variances or problems. Inspection without transparency is futile. The Scrum events are inspection points: Sprint Planning inspects the Product Backlog and selects what to build. The Daily Scrum inspects progress toward the Sprint Goal. The Sprint Review inspects the Increment. The Sprint Retrospective inspects the team's process and relationships.
Adaptation means that if any aspect of a process deviates outside acceptable limits—or if the resulting product will be unacceptable—the process or the material being produced must be adjusted. Adjustment must be made as soon as possible to minimize further deviation. This is why the Sprint Retrospective produces actionable improvements: inspection without adaptation is just diagnosis. The Scrum Master is accountable for helping the Scrum Team understand the importance of adaptation, especially in organizations where "we've always done it this way" overrides empirical learning.
How the Pillars Map to Specific CSM Exam Scenarios
The CSM exam presents scenarios and asks whether a Scrum Master's action appropriately applies Scrum theory. Understanding which pillar a given action serves helps you reason through the right answer.
Scenario: A team's Daily Scrum has become a status report to the manager who attends every day. Developers share updates directed at the manager rather than each other. What should the Scrum Master do?
The correct response connects to Transparency and Inspection. The Daily Scrum should create transparency among Developers about progress toward the Sprint Goal, and enable the Developers to inspect that progress themselves. A manager-directed status report doesn't serve this function—it serves the manager's visibility needs, not empirical process control. The Scrum Master should coach the team on the purpose of the Daily Scrum and address the manager's attendance pattern by offering alternative ways to get the information they need.
Scenario: A team consistently adds the Sprint Retrospective's improvement items to the "someday" backlog instead of the next Sprint Backlog. What pillar is failing?
Adaptation. The team is inspecting (they're identifying improvements) but not adapting (they're not implementing improvements). The Scrum Master should help the team commit to at least one concrete improvement per Sprint and include it in the Sprint Backlog with a Definition of Done that makes the improvement verifiable.
The Five Scrum Values and Their Relationship to Empiricism
The Scrum Guide lists five Scrum values: Commitment, Focus, Openness, Respect, and Courage. These values aren't separate from empiricism—they're the cultural conditions that make empiricism possible on a team.
Openness supports Transparency. Teams that aren't open about impediments, failures, and uncertainty can't create the transparency that inspection requires. Courage supports Adaptation. It takes courage to say "our approach isn't working" or "this Sprint Goal should be cancelled" or "I was wrong about this technical decision." Without courage, teams hide problems and empirical process control fails silently. Respect supports all three pillars by creating the psychological safety needed for honest inspection.
CSM exam questions about values often test whether a Scrum Master recognizes when a team's culture is undermining the empirical foundation of Scrum—and what they should do about it. The answer is rarely to apply a process fix; it's usually to address the cultural or interpersonal dynamic that's creating the problem.
Why "Following Scrum" Isn't the Same as Practicing Empiricism
Many teams run Sprints, hold Daily Scrums, and do Retrospectives without achieving empirical process control. The ceremonies are present; the empiricism is absent. This happens when teams treat Sprint Reviews as demos to check a box rather than genuine feedback sessions. It happens when Sprint Goals are vague ("work on the platform") rather than specific enough to be inspected. It happens when Retrospective improvements are never implemented.
The Scrum Guide says that Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made. If a team's Scrum implementation is revealing nothing—no impediments, no surprises, no learnings—something is wrong. Either the team is hiding problems, or the Scrum events aren't creating genuine transparency and inspection.
The CSM exam rewards candidates who understand this distinction: the ceremony of Scrum is not the same as the practice of Scrum. A Scrum Master's job is to help teams achieve the latter.
SimpuTech's CSM AI tutor includes scenario-based questions built around empiricism, the three pillars, and the Scrum values—so you can test your understanding beyond the definitions. Try it free before your exam.
Want to see how empiricism connects to the specific events and artifacts? Read Sprint Events and Artifacts: A Visual Guide for CSM Candidates.
Certification details verified against scrumalliance.org as of March 2026. Requirements and fees are subject to change—confirm current details at scrumalliance.org before registering.
Ready to put this into practice?
SimpUTech's Certified Scrum Master (CSM) AI Study Coach gives you personalized practice, instant explanations, and a study plan that adapts to your level.
Start Your Free 3-Day Trial