The 5 Scrum Values: A Guide for Scrum Master Exam Success (2026)

If you've been studying for the PSM I or CSM exam, you've probably memorized the Scrum framework's events, artifacts, and roles without too much trouble. But here's where many candidates stumble: the situational questions. These are the ones that describe a team conflict, a sprint in trouble, or a stakeholder demanding something mid-Sprint — and ask you what a Scrum Master should do. Getting these right requires more than memorization. It requires understanding the soul of Scrum, which lives in its five core values.

The 2020 Scrum Guide elevated the five values — Commitment, Focus, Openness, Respect, and Courage — to a foundational position in the framework. They're not soft suggestions or feel-good principles bolted onto the side. They're the behavioral operating system that makes Scrum work. Without them, you might have all the ceremonies and artifacts in place, but you won't have agility. And without understanding them deeply, you won't score well on the harder exam questions that separate the candidates who truly get Scrum from those who just learned the vocabulary.

This guide is built for serious candidates who want to walk into that exam confident they can handle whatever scenario gets thrown at them. We'll break down each value, connect it to real Scrum Master situations, and give you the exam mindset you need to apply these values correctly under pressure.

---

Why the 5 Scrum Values are Critical for Scrum Master Certification

The PSM I exam from Scrum.org is known for being scenario-based and genuinely challenging. The CSM exam from Scrum Alliance tends to be slightly more straightforward, but both test your ability to understand why Scrum works, not just what its components are. The five values are the "why."

The Scrum Guide 2020 states clearly: "Successful use of Scrum depends on people becoming more proficient in living five values." That word — living — is important. The guide isn't saying teams should understand the values theoretically. They should embody them in their daily behavior. When exam questions put you in the middle of a messy real-world situation, the correct answer almost always reflects one or more of these values being upheld or protected.

Here's the practical reality: many exam questions are designed to test whether you'll choose the comfortable, politically safe answer versus the answer that reflects genuine Scrum values. Candidates who haven't internalized the values tend to choose answers that sound reasonable on the surface — like "the Scrum Master should escalate the issue to management" — when the value-aligned answer requires more courage or a stronger commitment to self-management. Knowing the values deeply means you'll recognize those traps and avoid them.

The Connection Between Values and Scrum Pillars

The five values also directly support Scrum's three empirical pillars: Transparency, Inspection, and Adaptation. Openness supports Transparency. Commitment and Focus support the team's ability to Inspect progress meaningfully. Courage and Respect enable honest Adaptation without blame or defensiveness. When you see a question about sprint reviews going poorly or retrospectives producing no real change, ask yourself which pillar is being undermined — and which value could restore it.

---

Commitment: Aligning the Team with the Product Goal

Commitment in Scrum is frequently misunderstood, and that misunderstanding shows up in wrong exam answers. Many people interpret Commitment as "the team commits to finishing everything in the Sprint Backlog." That's not what the Scrum Guide says. The 2020 revision was deliberately updated to clarify this: the Development Team commits to the Sprint Goal, not to every single item on the Sprint Backlog.

This distinction matters enormously in practice — and on the exam. If a question describes a situation where a team realizes partway through a Sprint that they overestimated their capacity and won't finish all the Sprint Backlog items, the correct answer isn't to panic, work overtime, or report failure. It's to remain committed to delivering the Sprint Goal, adapt the plan as needed, and keep stakeholders informed.

What Commitment Looks Like in Real Teams

Imagine you're a Scrum Master and your team's Sprint Goal is to "enable users to complete the checkout flow." Three days into the Sprint, a developer discovers that a particular feature is far more complex than estimated. The team adjusts — they descope a lower-priority feature but stay laser-focused on delivering a working, tested checkout experience by Sprint's end. That's Commitment in action. They didn't commit to a task list; they committed to an outcome.

For exam purposes, watch for questions that pit individual task completion against team-level goal achievement. The value-aligned answer will almost always prioritize the Sprint Goal.

Key exam tip: When you see the word "commit" in an answer option, make sure it's referring to the goal, not to a fixed scope. Options that say the team "must commit to completing all Sprint Backlog items" are almost certainly wrong.

---

Focus: The Scrum Master's Role in Protecting the Sprint

Focus is the value that most directly ties to the Scrum Master's servant-leadership role as a protector of the Scrum Team. During a Sprint, the team's job is to make progress toward the Sprint Goal — and that requires protecting their attention from distractions, scope creep, and unnecessary interruptions.

This is where the Scrum Master earns their keep. A product owner receiving urgent requests from stakeholders mid-Sprint, a manager who wants a developer pulled for a "quick side project," a senior executive demanding a status update that requires the whole team to stop and prepare a presentation — these are all Focus killers. A good Scrum Master doesn't just shrug and say, "Well, management wants it." They find appropriate ways to shield the team while still respecting the legitimate needs of the organization.

Protecting the Sprint Without Being a Gatekeeper

There's an important nuance here that the exam will test: protecting Focus doesn't mean the Scrum Master becomes a bureaucratic wall. It means the Scrum Master helps the organization understand why unplanned interruptions cost more than they save, and works with the Product Owner to create proper channels for urgent requests — like adjusting the Sprint Backlog with Product Owner involvement, or in extreme cases, canceling the Sprint if the Goal becomes obsolete.

Consider this scenario: halfway through a Sprint, a major client requests a critical bug fix that wasn't planned. A Focus-aligned Scrum Master response would be to work with the Product Owner to assess the urgency, determine whether the Sprint Goal can still be met, and decide collaboratively whether to add the work (and what to remove), or whether the situation warrants a Sprint cancellation. What they wouldn't do is unilaterally add the work, or ignore the client's needs entirely.

Exam mindset: If an answer option has the Scrum Master making unilateral decisions about what gets added or removed from the Sprint Backlog, that's wrong — that's the Product Owner's domain. The Scrum Master facilitates; they don't dictate product decisions.

---

Openness: Building Transparency for Stakeholders and Teams

Openness is the value that enables Scrum's empirical process to function. If team members aren't open about impediments, progress, or struggles, the Sprint Review becomes a theater performance rather than a genuine inspection. If the Product Owner isn't open about changes in business direction, the team can't adapt. If the Scrum Master hides problems from stakeholders to avoid uncomfortable conversations, the whole system breaks down.

The Scrum Guide 2020 describes Openness as being open about all the work and the challenges encountered. This applies internally (within the Scrum Team) and externally (with stakeholders). A Sprint Review, for instance, is explicitly designed to be an open, collaborative working session — not a polished demo designed to impress. The difference is subtle but significant.

Openness in the Daily Scrum

The Daily Scrum is perhaps the highest-frequency opportunity to practice Openness. When a developer says "I'm fine, no blockers" when they're actually stuck and too embarrassed to ask for help, that's a failure of Openness. It seems harmless in the moment, but it can torpedo a Sprint Goal by Day 8. The Scrum Master's role is to create an environment where it feels safe to be honest about struggles — not to interrogate team members or run the Daily Scrum as a status report to management.

Real-world scenario: A Scrum Master notices that the same developer gives identical "all good" updates three days in a row, while the Scrum Board shows no movement on their tasks. An Openness-driven response is to have a private, supportive conversation — not to call them out publicly, and definitely not to report the issue to their manager without speaking to them first. This is also where Respect and Courage come into play simultaneously, which is why the values work as an interconnected system.

---

Respect: The Key to Successful Self-Management

Respect is the foundation of self-management, and self-management is one of the most tested concepts in PSM I exam questions. In Scrum, the Developers are responsible for managing their own work. No one tells them how to do their jobs, who picks up which task, or exactly how to architect a solution. This only works when team members genuinely respect each other's capabilities and judgment.

The Scrum Guide 2020 describes Scrum Team members as respecting each other as capable, independent people. This has direct implications for how a Scrum Master operates. A Scrum Master who micromanages task assignments, dictates technical approaches, or undermines a developer's decision in front of stakeholders is violating the value of Respect — even if they have the best intentions.

Respect Across Scrum Team Boundaries

Respect also extends outward. Developers need to respect the Product Owner's accountability for product decisions, even when they disagree with prioritization. The Product Owner needs to respect that the Developers are the experts on how to build, not just what to build. The Scrum Master needs to respect both, while also helping stakeholders understand why bypassing the Product Owner or pressuring the team directly isn't acceptable.

Exam tip: Questions about team members going around the Product Owner to get features added, or managers assigning tasks directly to developers, are Respect violations. The correct Scrum Master response is to address the behavior systemically — through coaching, education, and establishing clear team agreements — not to ignore it or simply remind people of the "rules."

---

Courage: Navigating Conflict and Difficult Decisions

Courage is the value that most distinguishes a great Scrum Master from a mediocre one — and it's also one of the most commonly tested on the exam. Courage in Scrum means doing the right thing even when it's uncomfortable. It means a Scrum Master having a difficult conversation with a senior manager who keeps bypassing the Product Owner. It means a developer saying "I think we're building the wrong thing" during Sprint Planning. It means the Product Owner removing a beloved feature from the backlog because the data doesn't support it.

The Scrum Guide explicitly connects Courage to working on tough problems, but in practice it shows up most visibly in interpersonal and organizational conflict. Scrum exposes dysfunction — that's actually one of its design features. And when it does, someone needs the Courage to name what's happening and address it.

Courage in Retrospectives

The Retrospective is the primary event for practicing Courage. A retrospective where everyone says "things are fine, we just need to communicate better" every Sprint isn't a real retrospective. It's conflict avoidance dressed up as process improvement. A Scrum Master with Courage creates space for the team to surface real problems — and then helps them commit to genuine experiments that address root causes.

Common exam trap: When a question describes a dysfunctional situation and offers an answer where the Scrum Master defers to management, avoids the conversation, or waits for someone else to fix it — that's almost always wrong. Scrum Masters aren't passive. They're courageous advocates for the team and the process.

---

How to Answer Scrum Values Questions on the PSM I Exam

Understanding the values conceptually is half the battle. Applying them under exam pressure is the other half. Here's a practical framework for approaching situational questions:

1. Identify the tension. Most situational questions describe a conflict between two legitimate interests — business urgency vs. team focus, individual opinion vs. team decision, transparency vs. comfort. Name the tension before you look at the answers.

2. Ask which value is being tested. Once you see the tension, it usually points to one or two primary values. A question about a manager demanding daily status reports is about Openness and Respect. A question about a developer refusing to follow a technical standard set by management is about Courage and self-management.

3. Eliminate anti-Scrum answers first. Options that involve the Scrum Master making unilateral product decisions, escalating to management as a first response, or ignoring team dysfunction are almost always wrong.

4. Choose the servant-leadership response. The correct answer will almost always have the Scrum Master coaching, facilitating, educating, or creating space — not commanding, deciding, or rescuing.

5. Check the answer against the Scrum Guide. If an answer option contradicts something explicitly stated in the 2020 Scrum Guide, eliminate it regardless of how reasonable it sounds.

---

Key Takeaways

• The five Scrum values — Commitment, Focus, Openness, Respect, and Courage — are foundational to understanding Scrum, not supplementary.
• Commitment is to the Sprint Goal, not to a fixed list of tasks.
• Focus requires the Scrum Master to protect the team from distractions and unplanned work, collaboratively with the Product Owner.
• Openness enables Transparency, which enables real Inspection and Adaptation.
• Respect supports self-management by honoring each role's accountabilities and each person's capabilities.
• Courage allows teams and Scrum Masters to surface and address dysfunction, conflict, and uncomfortable truths.
• Situational exam questions almost always have a value-aligned "right" answer and a comfortable-but-wrong answer. Learn to tell them apart.

---

Summary: Living the Values to Achieve Agility

The five Scrum values aren't exam trivia — they're a description of how high-performing agile teams actually behave. When you see a team that consistently delivers, adapts well to change, and genuinely improves every Sprint, you'll find these values operating underneath everything they do. The Scrum ceremonies and artifacts are just the structure; the values are what give that structure meaning.

For your exam preparation, the most powerful thing you can do after reading this guide is practice with realistic, scenario-based questions that force you to apply these values in context. Reading about Courage is different from choosing the courageous answer when three other options all sound plausible. Scenario practice builds the mental muscle memory you need to answer quickly and confidently on exam day.

Keep the values close as you study. When you encounter a practice question and you're not sure why one answer is better than another, map it back to the values. Nine times out of ten, the best answer will reflect a Scrum Master who is courageous, focused, open, respectful, and committed to the team's success — not their own authority or their organization's comfort.

---

Frequently Asked Questions

Q: Do the five Scrum values appear directly as questions on the PSM I exam, or only indirectly through scenarios?

A: Mostly indirectly. You're unlikely to see a question that simply asks "what are the five Scrum values?" Instead, scenarios will test whether you understand how to apply them. For example, a question might describe a situation where the team is pressured to hide a technical failure from stakeholders, and you'll need to recognize that the correct response involves Openness and Courage — even if those words never appear in the question.

Q: What's the most commonly tested Scrum value on the PSM I exam?

A: Based on the structure of Scrum.org's open assessments and common exam feedback, Commitment and Courage tend to appear most frequently in tricky scenarios. Commitment because of the common misconception about committing to scope rather than goals, and Courage because questions about conflict, dysfunction, and difficult conversations require candidates to choose assertive servant-leadership responses over passive or management-dependent ones.

Q: How do the five values relate to the three pillars of empiricism (Transparency, Inspection, Adaptation)?

A: They're deeply interconnected. Openness directly enables Transparency — teams can't have a transparent process if members aren't open about progress and problems. Commitment and Focus support meaningful Inspection by ensuring the team is actually working toward something inspectable. Courage and Respect enable genuine Adaptation — it takes courage to admit something isn't working, and respect to create the psychological safety that makes honest retrospectives possible. Understanding these connections will help you see the Scrum framework as a unified system, which is exactly what the harder exam questions reward.