Empiricism and Scrum Values in Practice: A Comprehensive Guide for PSM II
Introduction
Empiricism and the Scrum Values form the philosophical and behavioral foundation of the Scrum framework. While PSM I tests your knowledge of what these concepts are, PSM II challenges you to demonstrate a deep understanding of how they manifest in real-world practice, why they matter, and how to recognize when they are being upheld or violated. This guide will prepare you to confidently answer complex scenario-based questions on these topics.
Why Empiricism and Scrum Values Are Important
Without empiricism, Scrum becomes nothing more than a set of ceremonies performed mechanically. Without the Scrum Values, teams lack the behavioral compass needed to navigate complexity. Together, they are the engine and the steering mechanism of Scrum.
Here is why they matter:
- Complex work cannot be fully predicted. Empiricism acknowledges this reality and provides a disciplined approach to inspect and adapt based on real outcomes rather than theoretical plans.
- Trust enables transparency. The Scrum Values (Commitment, Focus, Openness, Respect, and Courage) create the psychological safety necessary for true transparency, which is the first pillar of empiricism.
- Without values, the pillars collapse. If team members lack courage, they will hide problems (destroying transparency). If they lack openness, inspection becomes superficial. If they lack commitment, adaptation never happens.
- Organizational agility depends on both. Organizations that embrace empiricism and live the Scrum Values are better positioned to respond to market changes, customer needs, and emerging risks.
What Is Empiricism in Scrum?
Empiricism means that knowledge comes from experience and making decisions based on what is observed. Scrum is founded on empirical process control theory, which rests on three pillars:
1. Transparency
Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires these aspects to be defined by a common standard so observers share a common understanding. Examples include:
- A clearly articulated Product Goal and Sprint Goal
- A visible and up-to-date Product Backlog and Sprint Backlog
- A shared Definition of Done that everyone understands and applies consistently
- Honest reporting of progress, impediments, and risks
2. Inspection
Scrum artifacts and progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. Inspection should not be so frequent that it gets in the way of the work. Key inspection points include:
- The Daily Scrum (inspecting progress toward the Sprint Goal)
- The Sprint Review (inspecting the Increment and progress toward the Product Goal)
- The Sprint Retrospective (inspecting the team's processes, interactions, and tools)
3. Adaptation
If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation. Examples include:
- Adjusting the Sprint Backlog during a Sprint when new information emerges
- Reordering the Product Backlog based on stakeholder feedback in the Sprint Review
- Changing team practices based on insights from the Sprint Retrospective
- A Scrum Master coaching the team to address a dysfunctional pattern immediately rather than waiting
What Are the Scrum Values?
The five Scrum Values are: Commitment, Focus, Openness, Respect, and Courage. They are not abstract ideals — they are behavioral expectations that directly enable empiricism.
Commitment
The Scrum Team commits to achieving its goals and to supporting each other. This does not mean committing to a fixed scope — it means committing to the Sprint Goal, to quality (the Definition of Done), and to continuous improvement. Commitment gives meaning to adaptation because the team is dedicated to acting on what they learn.
Focus
Everyone focuses on the work of the Sprint and the goals of the Scrum Team. Focus means the team concentrates on delivering the most valuable work and is not distracted by unrelated requests, multitasking, or premature optimization. Focus enables effective inspection because attention is directed toward what matters most.
Openness
The Scrum Team and its stakeholders are open about all the work and the challenges with performing the work. Openness is the behavioral foundation of transparency. Without openness, impediments stay hidden, risks go unaddressed, and the Product Backlog does not reflect reality.
Respect
Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. Respect creates the environment where people feel safe to be transparent, to raise concerns, and to offer differing opinions. It directly supports all three pillars of empiricism.
Courage
Scrum Team members have the courage to do the right thing and work on tough problems. Courage is essential for adaptation — it takes courage to acknowledge that a current approach is failing, to push back on unrealistic demands, to raise uncomfortable truths, and to make difficult decisions about the product or process.
How Empiricism and Scrum Values Work Together in Practice
Understanding how these concepts interrelate is critical for PSM II. Here are practical examples of how they work together:
Scenario 1: A team discovers mid-Sprint that the Sprint Goal is no longer achievable.
- Transparency: The Developers openly communicate this finding to the Product Owner and Scrum Master.
- Courage: It takes courage to admit the goal is at risk rather than silently cutting corners on quality.
- Openness: The team is honest about the root cause — perhaps they underestimated complexity or an external dependency failed.
- Inspection and Adaptation: The Product Owner and Developers collaborate to determine if the Sprint Goal can be renegotiated or if the scope of work should be adjusted.
- Respect: The Product Owner respects the Developers' professional judgment about what is achievable.
Scenario 2: A stakeholder pressures the team to skip testing to meet a deadline.
- Courage: The Developers have the courage to refuse to compromise the Definition of Done.
- Commitment: The team is committed to quality and to the shared standards they have agreed upon.
- Transparency: The team makes visible the trade-offs and risks of cutting quality (technical debt, potential defects, reduced trust).
- Adaptation: Rather than compromising quality, the team might adapt by reducing scope and delivering fewer but fully done items.
Scenario 3: During a Sprint Retrospective, a team member raises a concern about another member not pulling their weight.
- Courage: Raising interpersonal issues is difficult but necessary.
- Openness: The team discusses the concern without defensiveness.
- Respect: The conversation happens with respect for the individual, focusing on behaviors and outcomes rather than personal attacks.
- Inspection: The team examines what might be causing the issue — is it a skills gap, unclear expectations, personal circumstances, or an uneven distribution of work?
- Adaptation: The team agrees on concrete actions to improve, such as pair programming, redistributing work, or providing coaching.
Scenario 4: The Product Owner discovers through Sprint Review feedback that a major assumption about user needs was wrong.
- Transparency: The feedback from stakeholders and users is gathered and shared openly.
- Inspection: The Product Owner evaluates the impact on the Product Backlog and Product Goal.
- Courage: It takes courage to pivot away from a direction the team has invested effort in.
- Adaptation: The Product Backlog is reordered significantly to reflect the new understanding. The Product Goal may even need to be revised.
- Commitment: Despite the change, the team remains committed to delivering maximum value.
Common Anti-Patterns That Violate Empiricism and Scrum Values
Recognizing anti-patterns is essential for PSM II. Watch for these:
- Hidden impediments: When team members do not feel safe raising blockers, transparency is broken (violation of openness and courage).
- Zombie Scrum: Going through the motions of Scrum events without genuine inspection and adaptation — the rituals happen but nothing changes.
- Fake Done: Declaring work complete when it does not meet the Definition of Done destroys transparency and undermines commitment.
- Management overriding Sprint Goals: When managers or stakeholders add unplanned work without the team's agreement, it shows a lack of respect for the team's self-management and focus.
- Blame culture: If failures lead to blame rather than learning, courage and openness disappear, and the team stops being transparent.
- Cherry-picking metrics: Only reporting favorable data to stakeholders undermines transparency.
- Avoiding difficult conversations: When the Scrum Master or team avoids addressing dysfunction, adaptation cannot occur (violation of courage).
The Scrum Master's Role in Fostering Empiricism and Scrum Values
As a PSM II candidate, you are expected to understand how a Scrum Master actively fosters these principles:
- Coaching the team to understand why the values matter, not just memorizing them.
- Creating safe environments where people can be open and courageous without fear of punishment.
- Modeling the values through their own behavior — being transparent, courageous in addressing organizational impediments, and respectful in all interactions.
- Removing organizational impediments that prevent empiricism (e.g., reporting structures that incentivize hiding problems, or policies that prevent transparency).
- Facilitating meaningful Scrum events that enable genuine inspection and adaptation, not just going through the motions.
- Helping the organization understand that empiricism requires patience and trust — outcomes emerge through iteration, not through detailed upfront planning.
Exam Tips: Answering Questions on Empiricism and Scrum Values in Practice
1. Always connect values to pillars. PSM II questions often present scenarios where something is going wrong. Ask yourself: which pillar of empiricism is being undermined, and which Scrum Value is being violated? The correct answer will typically address the root cause at the values level, not just the symptom.
2. Look for the answer that enables self-management. PSM II favors answers where the Scrum Master coaches, facilitates, and empowers rather than directs, controls, or solves problems for the team. If an answer says the Scrum Master should tell the team what to do, it is likely wrong.
3. Favor transparency as the first step. In many scenarios, the best first action is to make information visible. You cannot inspect what you cannot see, and you cannot adapt if you haven't inspected. When in doubt, start with transparency.
4. Remember that adaptation requires courage. The best answer often involves the harder, braver path — having a difficult conversation, pushing back on a stakeholder, or acknowledging a failure. Avoid answers that choose comfort over improvement.
5. Understand the difference between commitment to goals and commitment to scope. PSM II tests whether you understand that Scrum Teams commit to the Sprint Goal, not to a fixed list of Product Backlog items. Answers that conflate these concepts are traps.
6. Beware of partial truths. Some answer options will correctly identify a Scrum Value but apply it in a way that contradicts empiricism. For example, an answer might invoke respect as a reason to avoid giving difficult feedback — but true respect includes being honest with people. Evaluate answers holistically.
7. Think about what a mature Scrum Master would do. PSM II is a professional-level certification. The expected behavior is that of an experienced Scrum Master who understands nuance. Avoid overly simplistic answers and look for responses that demonstrate systemic thinking.
8. Consider the long-term impact. PSM II often presents scenarios with a quick fix and a sustainable fix. Choose the sustainable fix. For example, if a team is struggling with transparency, the long-term answer is to build trust and model openness, not to implement surveillance or mandatory status reports.
9. Pay attention to who is involved. Empiricism in Scrum involves the entire Scrum Team and stakeholders. Watch for answers that exclude relevant parties — for example, adapting the process without involving the Developers, or making product decisions without the Product Owner.
10. Use the Scrum Guide as your source of truth. The Scrum Guide explicitly states that the Scrum Values give direction to the Scrum Team with regard to their work, actions, and behavior. When evaluating answers, ask: does this align with what the Scrum Guide says about how values support empiricism? If it contradicts the Scrum Guide, it is wrong regardless of how reasonable it might sound in practice.
Summary
Empiricism and the Scrum Values are inseparable in practice. Transparency, Inspection, and Adaptation can only function when the team lives the values of Commitment, Focus, Openness, Respect, and Courage. For PSM II, you must demonstrate not just knowledge of these concepts but the ability to recognize them in complex scenarios, identify when they are being violated, and recommend responses that a professional Scrum Master would take. Always look for the answer that addresses the root cause, enables self-management, prioritizes transparency, and requires courage to implement.
