Overview
Scrum Theory is the third SMPC learning-objective area. The 2020 Scrum Guide says Scrum is founded on empiricism and lean thinking. Empiricism holds that knowledge comes from experience and that decisions should be based on what is observed. Lean thinking reduces waste and focuses on essentials. Scrum applies both through an iterative, incremental approach that optimizes predictability and controls risk.
The area then covers the three empirical pillars. Transparency means the process and the work are visible to those performing and receiving it. Inspection means artifacts and progress toward agreed goals are checked frequently and diligently to detect problems. Adaptation means that when something deviates outside acceptable limits, the process or product is adjusted as soon as possible. Each Scrum event is a formal opportunity to inspect and adapt, and each artifact is designed to maximize transparency.
How it's tested
Questions ask you to name the pillar that a practice supports, explain why Scrum uses short iterations, or identify which pillar is failing in a scenario. Some ask what happens when artifacts have low transparency or when inspection results are ignored. Expect careful wording around the order and purpose of the pillars.
-
Name the pillar
A practice such as a visible Sprint Backlog or a Sprint Review is described, and you pick transparency, inspection or adaptation.
-
Find the broken pillar
A team inspects but never changes anything, or reports hide problems, and you identify which pillar is missing.
-
Why iterative and incremental
You explain how short cycles and usable Increments improve predictability and control risk on complex work.
A team's Sprint Backlog shows every task as on track, but testers know several items are blocked and do not update the board. The Sprint Review then surprises stakeholders. Which pillar failed first? Inspection seems likely because problems were found late. However, inspection can only be as good as the information available. The root failure is transparency, which made the inspection misleading.
Topics 5
Official topics from the CertiProf outline, in outline order.
3.1 EmpiricismKnowledge from experience and decisions based on observation.
- What it means
- Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Scrum uses empirical process control rather than defined process control, because complex work cannot be fully planned in advance.
- What to understand
- Defined process control assumes the same inputs always produce the same outputs, as on an assembly line. Empirical control accepts uncertainty and relies on frequent feedback. Scrum creates that feedback through the Sprint, which limits how long the team works before checking reality. The iterative and incremental approach means each Sprint produces a usable Increment, so the team learns from real results and risk is controlled cycle by cycle.
- How it shows up
- Expect questions on why Scrum relies on short cycles or why a detailed upfront plan is not trusted for complex products.
- Common confusion
- Treating iterative and incremental as the same thing: iterations repeat a cycle, while increments add usable product.
3.2 Lean thinkingReducing waste and focusing on what adds value.
- What it means
- The 2020 Scrum Guide added lean thinking as a second foundation of Scrum alongside empiricism. Lean thinking, derived from Toyota production ideas, reduces waste and focuses on essentials.
- What to understand
- Partner courses list five lean principles: identify value from the customer's view, map the value stream, create flow, establish pull and pursue perfection. In Scrum this shows up as small batches of work, limiting work in progress, a clear Definition of Done that prevents hidden rework, and the Retrospective as a way to remove waste from the process. Common forms of waste include partially done work, extra features, handoffs, task switching, waiting and defects.
- How it shows up
- A question may ask which foundation, other than empiricism, the Scrum Guide names, or which practice reduces waste.
- Common confusion
- Thinking lean means cutting people or budgets rather than removing activities that add no value.
3.3 TransparencyMaking the process and the work visible.
- What it means
- Transparency means the emergent process and work must be visible to those performing the work as well as those receiving it. Important decisions are based on the perceived state of the three artifacts.
- What to understand
- Low transparency leads to decisions that diminish value and increase risk. The Guide says transparency enables inspection, and inspection without transparency is misleading and wasteful. Each artifact supports transparency through its commitment: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment. The Scrum Master helps by exposing hidden work and encouraging honest updates.
- How it shows up
- Scenarios with hidden blockers, unclear Done criteria or private backlogs usually point to transparency.
- Common confusion
- Assuming transparency means publishing reports to managers rather than shared visibility for the team and stakeholders.
3.4 InspectionChecking artifacts and progress frequently to detect problems.
- What it means
- Inspection means the Scrum artifacts and progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems.
- What to understand
- Scrum provides cadence for inspection through its five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Inspection should not be so frequent that it gets in the way of the work. The Guide says inspection enables adaptation, and that inspection without adaptation is considered pointless. Inspection is done by the Scrum Team and, at the Sprint Review, together with stakeholders.
- How it shows up
- Questions ask which events provide inspection or what inspection is meant to enable.
- Common confusion
- Thinking inspection is a quality-control gate run by an outside reviewer.
3.5 AdaptationAdjusting the process or product when something deviates.
- What it means
- If any aspect of a process deviates outside acceptable limits or the resulting product is unacceptable, the process or materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation.
- What to understand
- Adaptation becomes more difficult when the people involved are not empowered or self-managing. That is why the Guide expects the Scrum Team to adapt the moment it learns anything new through inspection. Examples include changing the Sprint Backlog after a Daily Scrum, reordering the Product Backlog after a Sprint Review, and adopting an improvement after a Retrospective.
- How it shows up
- Look for answers that act on new information quickly rather than waiting for the end of a phase.
- Common confusion
- Waiting until the next Sprint to adapt when the change can be made within the current Sprint.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Empiricism
Knowledge from experience; decisions from observation.
- Remember
- Scrum's primary foundation.
- Tested as
- Underlies most why-questions.
- Trap
- Choosing defined process control for complex work.
-
Lean thinking
Reduce waste and focus on essentials.
- Remember
- Added as a foundation in the 2020 Guide.
- Tested as
- Recall of Scrum's two foundations.
- Trap
- Naming Kanban or Six Sigma as the second foundation.
-
Iterative and incremental
Repeated cycles that each add usable product.
- Remember
- Optimizes predictability and controls risk.
- Tested as
- Explains the purpose of Sprints.
- Trap
- Treating the two words as synonyms.
-
Transparency
Process and work visible to doers and receivers.
- Remember
- Enables inspection.
- Tested as
- Hidden-work scenarios.
- Trap
- Equating it with status reporting upward.
-
Inspection
Frequent, diligent checks of artifacts and progress.
- Remember
- Enables adaptation; should not disrupt work.
- Tested as
- Event-purpose questions.
- Trap
- Expecting an external auditor to do it.
-
Adaptation
Adjust as soon as possible when deviation is found.
- Remember
- Harder when people are not empowered.
- Tested as
- Timing and authority questions.
- Trap
- Delaying change to the next phase.
-
Pillar dependency
Transparency enables inspection, which enables adaptation.
- Remember
- Inspection without transparency misleads; without adaptation it is pointless.
- Tested as
- Find-the-broken-pillar items.
- Trap
- Blaming inspection when information was hidden.
-
Defined process control
Same inputs always give the same outputs.
- Remember
- Suits repeatable work, not complex products.
- Tested as
- Contrast with empiricism.
- Trap
- Applying it to novel product development.
-
Waste
Any activity that adds no customer value.
- Remember
- Partially done work and extra features are classic forms.
- Tested as
- Lean scenario questions.
- Trap
- Treating all documentation as waste.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
The three pillars
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Transparency | Visible process and work | Comes first; makes inspection meaningful | Limiting it to management reports |
| Inspection | Frequent checks against goals | Uses transparent information to find variance | Running it without acting on results |
| Adaptation | Prompt adjustment of process or product | Turns inspection findings into change | Postponing it until a later phase |
Empirical vs. defined process control
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Empirical | Learn by doing and observing | Frequent feedback loops | Thinking it means no planning |
| Defined | Follow a fixed, repeatable procedure | Assumes predictability upfront | Choosing it for uncertain products |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Blame inspection
- What candidates pick
- Inspection as the failing pillar when information was hidden.
- Why it looks right
- Problems were discovered late.
- Why it's wrong
- Inspection only works on transparent information; the first failure is transparency.
Clue to watch for Hidden blockers or inaccurate boards.
-
Empiricism only
- What candidates pick
- Empiricism as Scrum's only foundation.
- Why it looks right
- Older guides only mentioned empiricism.
- Why it's wrong
- The 2020 Guide states Scrum is founded on empiricism and lean thinking.
Clue to watch for A question asking for the foundations, plural.
-
Inspect constantly
- What candidates pick
- Inspecting as often as possible.
- Why it looks right
- More checking seems safer.
- Why it's wrong
- The Guide says inspection should not be so frequent that it gets in the way of work.
Clue to watch for Proposals for hourly status checks.
-
Adapt later
- What candidates pick
- Waiting for the Retrospective to fix an obvious issue.
- Why it looks right
- The Retrospective is the improvement event.
- Why it's wrong
- Adaptation should happen as soon as possible; the Retrospective is not the only opportunity.
Clue to watch for A problem found mid-Sprint.
-
Predict with a detailed plan
- What candidates pick
- A full upfront plan to make complex work predictable.
- Why it looks right
- Plans feel controlled.
- Why it's wrong
- Scrum gains predictability through short empirical cycles and usable Increments, not upfront certainty.
Clue to watch for Words like novel, uncertain or complex.
Answer framework
Use these steps for theory questions about pillars, foundations and why Scrum works the way it does.
- Decide whether the question is about information being made visible, information being checked against a goal, or findings being acted on.
- Map visibility to transparency, checking to inspection and acting to adaptation, then confirm the dependency order before choosing the failing pillar.
- If the scenario has hidden or inaccurate information, choose transparency even when problems surfaced at an inspection.
- For questions about the basis of Scrum, remember that the 2020 Guide names two foundations: empiricism and lean thinking, not empiricism alone.
- Prefer answers that shorten feedback loops and act on new information quickly over answers that rely on upfront prediction.
Practice question
Want more like this? The SMPC practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Read the Scrum Theory section of the 2020 Scrum Guide until you can reproduce its structure: two foundations, an iterative and incremental approach, three pillars and the statements linking them. The Guide's sentences on what happens without transparency or without adaptation are especially useful for elimination on the exam.
Draw a simple chain on paper: transparency, then inspection, then adaptation. Under each pillar list the artifacts, commitments and events that support it. This makes it easy to answer which-pillar questions and connects theory to the later areas on events and artifacts.
For lean thinking, write down the five lean principles and seven common forms of waste with one Scrum example each, such as partially done work hidden from the Increment. Then practise with scenarios: describe a team problem in one line and name the pillar or foundation involved. Ten such examples are usually enough to make this area automatic, and they also prepare you for event questions later.
FAQ
What share of SMPC questions come from Scrum Theory?
CertiProf does not publish weights for Scrum Theory or any other SMPC area. Because theory explains many other rules, expect a few direct questions, roughly four, and indirect use in event and artifact questions.
What are the foundations of Scrum?
The 2020 Scrum Guide names empiricism and lean thinking. Earlier guides mentioned only empiricism.
What are the three pillars of Scrum?
Transparency, inspection and adaptation. Transparency enables inspection, and inspection enables adaptation.
Are the pillars the same as the Scrum values?
No. The pillars are about empirical process control. The five values are commitment, focus, openness, respect and courage, covered in the next area.
Why does Scrum use short Sprints?
Short cycles create frequent inspection points, limit risk to one Sprint's investment and improve predictability through observed results.
Is iterative the same as incremental?
Not quite. Iterative means repeating a cycle; incremental means each cycle adds usable product. Scrum uses both.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 3 knowledge
Run a quick SMPC set on empiricism, lean thinking and the three pillars to check you can find the broken pillar in a scenario.