SkarpChapter 2 of 10
Scrum Theory: Empiricism, Complexity, and the Scrum Values
Enter the world of complex work where prediction fails and empiricism rules, and see why Scrum’s simple rules and five values are non‑negotiable for both the exam and real teams.
Step 1: Why Scrum Needs Empiricism
Scrum and Empiricism
Scrum is based on empirical process control: we learn by doing and adjust based on evidence, not on detailed predictions made months earlier.
Three Pillars
The current Scrum Guide (updated Nov 2020) defines empiricism with three pillars: Transparency, Inspection, and Adaptation. These support all of Scrum.
Complex Work
Scrum targets complex work: requirements change, technology evolves, and cause-and-effect are only clear in hindsight. Long-term detail plans become guesses.
Exam Relevance
For PSM I, be ready to define empiricism, spot when it is needed, and map Scrum events and artifacts to transparency, inspection, and adaptation.
Step 2: Complex vs. Complicated Work (Why Scrum Fits)
Types of Work
Think in three buckets: simple, complicated, and complex work. Scrum is designed for the third: complex work, where prediction fails.
Simple and Complicated
Simple: clear steps, known best practices (e.g., a recipe). Complicated: requires experts, but can still be planned (e.g., a bridge design). Scrum is rarely needed here.
Complex Work
Complex: many interacting factors, shifting requirements, and cause-and-effect only clear in hindsight (e.g., new digital products in changing markets).
Why Scrum Fits
Scrum fits complex work: short Sprints, incremental delivery, and empiricism (probe–sense–respond) instead of heavy up-front prediction.
Step 3: The Three Pillars – Transparency, Inspection, Adaptation
Three Pillars Overview
Empiricism in Scrum stands on three pillars: Transparency, Inspection, and Adaptation. If one is weak, empiricism breaks.
Transparency
Transparency means the real state of product, work, and process is visible and understandable. Without it, inspection is misleading or useless.
Inspection
Inspection is frequently checking Scrum artifacts and progress toward goals to spot problems early, but not so often that it blocks doing work.
Adaptation
Adaptation is changing plans, scope, or process quickly when inspection shows things are off, to avoid more waste or deviation.
Step 4: How Scrum Events Support Empiricism
Events and Empiricism
Each Scrum event reinforces empiricism. Think: how does each event increase Transparency, enable Inspection, and trigger Adaptation?
Sprint & Planning
The Sprint gives a short learning cycle. Sprint Planning: inspect Product Backlog and capacity, then adapt by selecting work and defining a Sprint Goal.
Daily Scrum
At the Daily Scrum, Developers make progress and impediments transparent, inspect progress toward the Sprint Goal, and adapt their plan for the next 24 hours.
Review & Retro
Sprint Review: inspect the Increment with stakeholders and adapt the Product Backlog. Sprint Retrospective: inspect how we worked and adapt our process.
Step 5: Quick Thought Exercise – Spot the Broken Pillar
Consider each scenario and decide which pillar of empiricism is most clearly broken (Transparency, Inspection, or Adaptation).
- Scenario A:
- The team rarely updates the Sprint Backlog.
- Management believes everything is on track.
- In reality, half the work is blocked, but nobody outside the team can see it.
- Scenario B:
- The team has a clear Product Backlog and visible Sprint Backlog.
- They never hold a Sprint Review and only show the product after 6 months.
- Scenario C:
- The team inspects progress daily and runs all Scrum events.
- Every Sprint Retrospective identifies the same recurring problem.
- They never actually change their way of working.
Your task:
- For each scenario, write down which pillar is most broken and why.
- Then check the suggested answers below.
Suggested answers (do not peek until you have tried):
- Scenario A: Transparency – the real status is hidden.
- Scenario B: Inspection – they are not inspecting the Increment frequently.
- Scenario C: Adaptation – they inspect but do not change behavior.
On the PSM I exam, when you see a problem, ask: is this mainly a transparency, inspection, or adaptation issue?
Step 6: The Five Scrum Values
Scrum Values Overview
Scrum has five values: Commitment, Focus, Openness, Respect, Courage. These guide behavior and make empirical Scrum possible.
Commitment & Focus
Commitment: to goals and professionalism, not fixed scope. Focus: on the Sprint Goal and team goals, saying no to distractions.
Openness & Respect
Openness: being honest about work and problems, enabling transparency. Respect: seeing teammates as capable, supporting collaboration.
Courage and Exam Link
Courage: to do the right thing and speak up. On the exam, many scenarios test which value is missing or which value a Scrum Master should encourage.
Step 7: Scrum Values in Action – Mini Scenarios
Commitment & Focus in Action
Commitment: team aligns around a Sprint Goal. Focus: they protect it from unrelated requests, explaining the impact of distractions.
Openness with Stakeholders
Openness: in the Sprint Review, the team shares changes, risks, and dropped items honestly so stakeholders can help adapt the Product Backlog.
Respect within the Team
Respect: seniors listen to juniors, ask questions, and help improve ideas instead of dismissing them. This supports learning and collaboration.
Courage toward Leadership
Courage: the Scrum Master challenges harmful patterns (like constant scope changes) and proposes Scrum-consistent alternatives.
Step 8: Quiz – Empiricism in Practice
Test your understanding of empiricism and Scrum events.
During a Sprint, the Developers realize that a key assumption about user behavior was wrong. What is the MOST Scrum-consistent response?
- Continue with the original plan to honor the Sprint commitment and avoid confusion.
- Immediately stop the Sprint and start a new one with updated assumptions.
- Inspect the impact on the Sprint Goal and adapt the plan within the current Sprint if possible.
- Ask the Product Owner to update the Product Backlog after the release, but finish the Sprint as planned.
Show Answer
Answer: C) Inspect the impact on the Sprint Goal and adapt the plan within the current Sprint if possible.
Scrum is empirical: when new information appears, the team should **inspect and adapt**. The Developers and Product Owner inspect the impact on the Sprint Goal and adapt the plan within the current Sprint if they can. Stopping the Sprint is reserved for the Product Owner and only when the Sprint Goal becomes obsolete.
Step 9: Quiz – Scrum Values in Scenarios
Match behaviors to Scrum values.
A Scrum Master notices that Developers are afraid to raise problems in the Daily Scrum because a manager sometimes criticizes them harshly. Which Scrum value should the Scrum Master emphasize FIRST?
- Focus
- Respect
- Commitment
- Openness
Show Answer
Answer: B) Respect
The core issue is a lack of **Respect**. Without respect, people will not feel safe to be open. Emphasizing respect (and coaching the manager) helps create a safe environment that then enables openness and transparency.
Step 10: Flashcards – Key Terms Review
Flip the cards (mentally or with a partner) to review core Scrum theory terms.
- Empiricism
- A way of working where decisions are based on observation, experience, and evidence rather than detailed prediction; in Scrum it relies on transparency, inspection, and adaptation.
- Transparency
- Making the true state of the product, work, and process visible and understandable to those inspecting it; a pillar of empirical process control.
- Inspection
- Frequent checks of Scrum artifacts and progress toward goals to detect undesirable variances; must not be so frequent that it disrupts work.
- Adaptation
- Adjusting plans, scope, or processes as soon as possible when inspection shows that aspects of the work are outside acceptable limits.
- Complex Work
- Work where cause and effect are only clear in hindsight, requirements change often, and prediction is unreliable; Scrum is designed for this environment.
- Scrum Values
- Five values described in the Scrum Guide: Commitment, Focus, Openness, Respect, Courage; they guide behavior and enable effective use of Scrum.
- Sprint Goal
- A single objective for the Sprint that provides focus and flexibility; the Developers commit to it and adapt their work to achieve it.
Key Terms
- Increment
- A concrete stepping stone toward the Product Goal; a usable piece of the product that meets the Definition of Done.
- Adaptation
- Changing plans, scope, or processes promptly in response to what is learned during inspection.
- Empiricism
- A decision-making approach based on observation, experience, and evidence rather than prediction; in Scrum, implemented through transparency, inspection, and adaptation.
- Inspection
- Regularly examining Scrum artifacts and progress toward goals to identify problems or deviations early.
- Scrum Event
- A formal opportunity to inspect and adapt artifacts and progress; includes the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
- Sprint Goal
- A single objective for the Sprint that provides focus to the Scrum Team and allows flexibility in how work is implemented.
- Complex Work
- Work in which cause and effect are not obvious in advance, requirements change frequently, and experimentation is needed; Scrum targets this type of work.
- Product Goal
- A long-term objective for the Scrum Team that provides a target for the Product Backlog and guides Sprints toward a larger outcome.
- Scrum Values
- Commitment, Focus, Openness, Respect, and Courage; behavioral principles that support successful Scrum.
- Transparency
- The state of having the true situation visible and understandable to those inspecting it; essential for meaningful inspection in Scrum.