Empiricism & the Scrum Values

PSM I PSM I · Scrum Theory & Values

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

Scrum rests on a single idea about how knowledge works: you learn the most from doing the work and watching what actually happens, not from planning everything in advance. This idea is called empiricism, and the Scrum Guide builds the entire framework on it, alongside lean thinking. Empiricism holds that knowledge comes from experience and that decisions should be based on what is observed. Lean thinking adds a second discipline: cut waste and keep attention on the essentials. Together they explain why Scrum works in short cycles instead of long plans. When a problem is complex — when requirements shift, technology surprises you, and nobody can predict the outcome reliably — the rational response is to take small steps, inspect the results honestly, and adjust. That is the whole engine of Scrum: an iterative, incremental approach that improves predictability and keeps risk under control by shortening the gap between doing something and learning from it.

Empiricism is put into practice through three pillars: transparency, inspection, and adaptation. They work as a loop, and each one depends on the others. Transparency means the emerging process and the work itself must be visible both to the people doing the work and to the people receiving it. Scrum's important decisions rest on how its three formal artifacts appear to be doing, so if an artifact hides the true state of things, every decision built on it is suspect. Low transparency leads to choices that reduce value and increase risk — for example, a Product Backlog that looks healthy because unfinished work is marked complete will produce release forecasts nobody can trust. Transparency is not a reporting exercise; it is a property of the artifacts and of how openly the team works. It requires honesty about progress, problems, and quality, even when the news is bad.

Inspection is the regular, careful examination of Scrum's artifacts and of progress toward agreed goals, looking for unwanted variation or problems. Scrum provides a rhythm for inspection through its five events: each event is a scheduled moment to look closely at something specific — the Sprint Backlog at the Daily Scrum, the Increment at the Sprint Review, the team's own way of working at the Sprint Retrospective. Two details matter for the exam. First, inspection must be frequent and diligent, carried out by people skilled enough to spot real problems. Second, inspection is pointless without adaptation: looking at something and then changing nothing is wasted effort, and Scrum's events are deliberately designed to provoke change. Inspection should also not interfere with the work itself — it is a way of seeing clearly, not a way of interrupting people.

Adaptation is what happens when inspection finds a problem. If some part of the process drifts outside acceptable limits, or the resulting product is not acceptable, then the process or the materials being produced must be adjusted — and the adjustment should happen as soon as possible, to keep further drift small. A team that discovers on day two of a Sprint that its technical approach will not work should change course on day two, not wait for the Sprint Review. The Guide adds a warning that matters for real teams: adaptation gets harder when the people involved are not empowered or self-managing. A team that must ask permission for every change cannot adapt quickly, which is why self-management is not a nice-to-have in Scrum but a precondition for empiricism to function. The Scrum Team is expected to adapt the moment it learns something new through inspection — that immediacy is the point of the whole loop.

The five Scrum Values

Scrum also depends on people living five values: commitment, focus, openness, respect, and courage. The Guide describes each in plain terms. The Scrum Team commits to achieving its goals and to supporting each other. Its primary focus is the work of the Sprint, so it can make the best possible progress toward its goals. The team and its stakeholders are open about the work and the challenges. Team members respect each other as capable, independent people, and are respected in the same way by the people they work with. And team members have the courage to do the right thing and to work on tough problems. These values give direction to the team's work, actions, and behavior. Notice the direction of the relationship: the values shape decisions and actions — the values are not a poster on the wall that the team occasionally consults, and they are not enforced by a manager. The Guide says explicitly that decisions, actions, and the way Scrum is played reinforce the values, not the other way around. The team learns and explores the values by working with Scrum's events and artifacts, and when the values are genuinely embodied by the team and the people around it, the three empirical pillars come to life and build trust.

How the exam tests this

PSM I questions on empiricism usually test whether you can tell the pillars apart and apply them to a situation. A team that marks work complete when it is not has a transparency problem, not an inspection problem. A team that holds a Sprint Review, hears that stakeholders are unhappy, and changes nothing has inspected without adapting. A team that cannot change its own plan without a manager's approval has an adaptation problem rooted in missing empowerment. Values questions work the same way: a developer who stays silent about a risk because they fear blame is missing courage and openness; a team that starts five initiatives at once is missing focus; a Product Owner who overrides the Developers' estimates without discussion is missing respect. The exam also tests the relationship between values and pillars: values are what make the pillars work in practice, because transparency without openness is impossible, and inspection without courage turns into polite agreement.

Worked scenario

Consider a Scrum Team building a payment feature. Halfway through the Sprint, the Developers realize the payment provider's API behaves differently from its documentation, and their planned approach will not work. An empiricism-driven team inspects the situation at the next Daily Scrum, adapts the Sprint Backlog, and tells the Product Owner what has changed so the Sprint Goal can be protected — perhaps by reducing scope in agreement with the Product Owner. A team that ignores empiricism instead hides the problem, keeps reporting progress against the original plan, and discovers at the Sprint Review that nothing usable was produced. The first team used all three pillars: transparency about the problem, inspection of progress toward the Sprint Goal, and adaptation of the plan. The second team failed at the first pillar, and everything downstream failed with it. That is why the pillars are tested so heavily: they are not abstract philosophy, they are the mechanism by which Scrum Teams deal with reality.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.Which statement BEST describes empiricism as it is used in Scrum?

Report an error

Q2.Scrum puts empiricism into practice through three pillars. Which set lists all three correctly?

Report an error

Q3.A Scrum Team marks Product Backlog items as complete even though the work does not meet the Definition of Done, because they want the Sprint to look successful. Which pillar of empiricism is MOST directly damaged?

Report an error

Q4.Which statement about inspection in Scrum is TRUE?

Report an error

Q5.According to the Scrum Guide, adaptation becomes more difficult when the people involved are:

Report an error

Q6.Which of the following is NOT one of the five Scrum Values?

Report an error

Q7.During a Sprint, a Developer notices a serious technical risk but says nothing in the Daily Scrum because they fear being blamed. Which Scrum Values are MOST clearly missing in this situation?

Report an error

Q8.Lean thinking, one of the two foundations of Scrum alongside empiricism, is BEST described as:

Report an error

Q9.Which statement BEST describes the relationship between the Scrum Values and the empirical pillars?

Report an error