Why this level matters
Empiricism is the theory that Scrum is built on. Most PSPO I scenario questions come down to one test: which option uses evidence to decide what to do next? If you learn the three pillars, and why each one needs the one before it, you can answer many of those questions without memorising them.
All quotations marked Scrum Guide come from the Scrum Guide 2020 by Ken Schwaber and Jeff Sutherland, licensed under CC BY-SA 4.0. The rest is our own explanation.
Step 1: Learn the two foundations word for word
Scrum theory has two foundations. Memorise both definitions exactly.
- Empiricism. Scrum Guide: "Empiricism asserts that knowledge comes from experience and making decisions based on what is observed."
- Lean thinking. Scrum Guide: "Lean thinking reduces waste and focuses on the essentials."
The Guide then says how Scrum puts these into practice. Scrum Guide: "Scrum employs an iterative, incremental approach to optimize predictability and to control risk."
Do this: Write the three quoted sentences from memory. If you can't, learn them again before you go on. The exam often offers answer options that are nearly right, such as "knowledge comes from detailed planning".
Step 2: Tell empirical work apart from predictive work
A predictive, plan-driven approach tries to know everything up front. It fixes the scope, the plan and the dates, and then measures how far the work deviates from the plan. An empirical approach accepts that complex product work is uncertain. It takes a small step, looks at the result and decides what to do next.
| Question | Predictive answer | Empirical answer |
|---|---|---|
| Where does knowledge come from? | Analysis done before the work starts | Experience and what is observed |
| When is the plan fixed? | At the start | It changes as you learn |
| How is risk controlled? | By sticking to the plan | Through short cycles and frequent inspection |
| What counts as progress? | Following the plan | A usable outcome that has been inspected |
Example: A Product Owner thinks small cafés would pay for a loyalty feature. A predictive team would specify the whole feature and build it over six months. An empirical team builds the smallest usable version, puts it in front of real users, measures how they use it, and then decides whether to extend it, change it or drop it.
Do this: When you read a scenario question, look for words that point to a predictive approach: "sign off the full scope", "lock the plan", "wait until everything is specified". Those options are usually wrong.
Step 3: Follow the chain of pillars
The Scrum Guide says the Scrum events work "because they implement the empirical Scrum pillars of transparency, inspection, and adaptation." The order matters because each pillar depends on the one before it.
- Transparency. The work and the process must be visible both to the people doing the work and to the people receiving it. Scrum Guide: "Artifacts that have low transparency can lead to decisions that diminish value and increase risk."
- Inspection. Scrum Guide: "Transparency enables inspection. Inspection without transparency is misleading and wasteful." The artifacts and the progress toward agreed goals are inspected "frequently and diligently", and the five events provide the regular cadence for it.
- Adaptation. Scrum Guide: "Inspection enables adaptation. Inspection without adaptation is considered pointless." Adjustments are made "as soon as possible to minimize further deviation", and "a Scrum Team is expected to adapt the moment it learns anything new through inspection."
Think of a car dashboard. A fuel gauge you can't trust (low transparency) makes checking it misleading. A gauge you read and then ignore (inspection without adaptation) changes nothing. You only benefit when the gauge is accurate, you look at it, and you act on what it shows.
One more condition: Scrum Guide: "Adaptation becomes more difficult when the people involved are not empowered or self-managing." A team that has to wait for outside approval adapts too late.
Step 4: Act empirically when you face uncertainty
When you are unsure about scope, value or timing, follow these steps:
- Make the current state visible. Make sure everyone sees the same honest information, including work that isn't finished. Don't report half-finished work as complete.
- Pick the smallest step that can produce evidence. Choose a small, usable piece of work that will answer the most important open question.
- Inspect the real result. Use actual usage, stakeholder feedback and measured progress, not opinions about what might happen.
- Adapt straight away. Reorder or change the Product Backlog as soon as the evidence calls for it. Don't wait for a quarterly plan review.
- Repeat. Each cycle reduces uncertainty and makes your next forecast better.
Example on timing: A stakeholder asks for a guaranteed release date for 40 backlog items. The empirical response is a forecast based on the progress the team has actually achieved so far. You say clearly that it is a forecast, and you update it every Sprint as new evidence arrives. You don't promise a fixed date.
Common traps
- "We inspect, so we're empirical." Not if nothing changes afterwards. That is inspection without adaptation, which the Guide calls pointless.
- "A detailed up-front plan reduces risk." In Scrum, short iterative and incremental cycles control risk.
- "Hide bad news until it's fixed." This lowers transparency, so every later inspection is misleading.
- "Lean means working faster." Lean thinking means reducing waste and focusing on the essentials. It is not about speed for its own sake.
What the exam asks about this
- You will see questions asking for the definitions of empiricism and lean thinking, often with distractors that sound predictive.
- You will see questions on the order of the pillars and how they depend on each other: transparency, then inspection, then adaptation.
- You will see scenarios where something hides the true state of the work, or where feedback is collected and then ignored. You must pick the option that restores transparency or adapts straight away.
- You will see questions about the Product Owner choosing between "plan everything first" and "learn by delivering and inspecting". Choose the empirical option.
Key takeaways
- Empiricism: knowledge comes from experience and from decisions based on what is observed.
- Lean thinking reduces waste and focuses on the essentials.
- Scrum's iterative, incremental approach optimises predictability and controls risk.
- Transparency enables inspection, and inspection enables adaptation. If you remove one pillar, the ones after it stop working.
- Inspection without transparency is misleading and wasteful. Inspection without adaptation is pointless.
- When you are uncertain, make the work visible, take a small step, inspect the result and adapt at once.