Unlocking High-Performance Teams: The 5 Core Scrum Values Explained

Many teams adopt Scrum ceremonies—daily stand-ups, sprint planning, retrospectives—but still struggle with low trust, missed commitments, or siloed behavior. The missing piece often isn't process but culture. The Scrum Guide defines five values that underpin every event and artifact: Focus, Courage, Openness, Commitment, and Respect. When these values are alive, teams self-organize, adapt quickly, and deliver consistently. This guide unpacks each value with real-world scenarios, trade-offs, and a step-by-step plan to embed them in your team's DNA. Last reviewed: May 2026.

Why Scrum Values Matter More Than Process

The Hidden Driver of Team Performance

Process frameworks provide structure, but values provide the energy. A team can follow sprint planning to the letter yet still fail if members don't feel safe to speak up (Openness) or if they avoid hard trade-offs (Courage). In a typical project, I've seen teams with perfect Jira boards but zero trust—they missed every sprint goal because no one was willing to say "we can't do this by Friday." That's a values gap, not a process gap.

Research from organizational psychology consistently shows that psychological safety—a close cousin of Openness and Respect—is the top predictor of team effectiveness. While we won't cite a specific study, many industry surveys suggest that teams with high psychological safety are more innovative and less prone to burnout. The Scrum values formalize these soft skills into a professional code.

Common Misconceptions

One misconception is that values are "nice-to-have" or only relevant for mature teams. In reality, values are most critical when a team is forming or under pressure. Another myth is that values are vague—they can be made concrete through behaviors. For example, Commitment isn't just saying "I'll try"; it's agreeing on a sprint goal and doing whatever is ethical to achieve it. Focus isn't multitasking; it's protecting the sprint backlog from scope creep.

To make values actionable, many teams create a "values charter" with specific do's and don'ts. For instance, under Openness, a team might agree: "We share incomplete work in the daily stand-up without fear of judgment." This transforms an abstract value into a daily habit.

Breaking Down Each Value: Definitions and Behaviors

Focus: The Art of Saying No

Focus means everyone concentrates on the work of the sprint and the sprint goal. In practice, this means limiting work in progress, avoiding context switching, and protecting the team from external interruptions. A common failure mode is the "hero" developer who works on multiple features simultaneously, thinking it's efficient—but it actually increases cycle time and defect rates. To cultivate Focus, teams can use a physical or digital "focus board" that shows only current sprint items, and the Scrum Master acts as a shield against stakeholder requests that don't align with the sprint goal.

Courage: Speaking Truth to Power

Courage is about doing the right thing, even when it's difficult. This includes admitting when a task is too complex, pushing back on unrealistic deadlines, and raising impediments early. In one composite scenario, a team member noticed a critical design flaw midway through a sprint. Instead of hiding it to avoid blame, she raised it in the daily stand-up. The team paused, re-estimated, and negotiated a scope reduction with the product owner. The result was a smaller but working increment rather than a broken feature delivered late. Courage also means having the guts to fail fast—to try a new approach in a sprint and abandon it if it doesn't work.

Openness: Transparency Builds Trust

Openness means being transparent about work, challenges, and progress. This goes beyond the Scrum artifacts (product backlog, sprint backlog, increment) to include interpersonal honesty. A team that practices Openness shares not only completed work but also unfinished work, mistakes, and lessons learned. For example, during a sprint review, a developer might show a partially working feature and explain the technical debt incurred—inviting feedback rather than hiding it. This value is especially important in distributed teams, where lack of visibility can breed suspicion. Tools like shared dashboards and daily video stand-ups help maintain openness across time zones.

Commitment: Ownership Over Agreement

Commitment is often misunderstood as a promise to deliver a fixed scope. In Scrum, commitment means dedicating yourself to achieving the sprint goal and supporting your teammates. It's not about blindly accepting all work; it's about collectively owning the outcome. A team that commits will renegotiate scope when new information arises, rather than silently failing. For instance, if a team discovers halfway through a sprint that a task will take twice as long, they don't just work overtime—they discuss with the product owner to adjust the sprint backlog. True commitment is flexible, not rigid.

Respect: The Foundation of Collaboration

Respect means valuing each person's skills, perspectives, and time. It shows up in how we listen during retrospectives, how we give constructive feedback, and how we handle disagreements. A lack of respect often manifests as blame, micromanagement, or ignoring quieter team members. To build respect, teams can establish a "no interruption" rule during discussions, use round-robin speaking orders, and celebrate diverse contributions. In one team I observed, a senior developer made a point to ask junior members for their opinions during sprint planning—this simple act boosted confidence and uncovered ideas that would have been missed.

Practical Steps to Embed Values in Your Scrum Events

Sprint Planning: Aligning Focus and Commitment

Start sprint planning by reviewing the team's values charter. For each proposed backlog item, ask: "Does this align with our current focus?" and "Can we commit to this given our capacity?" Use a structured format: first, the product owner presents the goal; then the team estimates and selects work; finally, the team collectively commits to the sprint goal. If a team member is uncomfortable with the commitment, that's a signal to renegotiate. A concrete technique is to use a "commitment vote"—each member holds up a green (yes), yellow (unsure), or red (no) card. Red cards trigger a discussion to resolve concerns before proceeding.

Daily Stand-Up: Reinforcing Openness and Courage

The daily stand-up is a prime opportunity to practice Openness and Courage. Instead of a status report, frame it as: "What did I do yesterday? What will I do today? What impediments do I see?" Encourage team members to share blockers early, even if they're uncomfortable. To prevent the meeting from becoming a reporting session, the Scrum Master can model vulnerability by sharing their own challenges first. Another technique is to rotate the facilitator role, so everyone practices leading with openness.

Sprint Review: Celebrating Respect and Openness

The sprint review is not a demo for praise—it's a feedback session. Respect means inviting honest critique from stakeholders without being defensive. To foster this, start the review by stating the sprint goal and showing what was accomplished, including unfinished work. Ask stakeholders: "What would you change?" and "What's missing?" If a stakeholder criticizes a feature, the team should listen without justifying—then capture the feedback for the product backlog. This builds trust and shows that the team values external perspectives.

Retrospective: Deepening All Five Values

Retrospectives are the heart of continuous improvement. Use a structured format like Start/Stop/Continue, but add a values check. For example, in the "Stop" column, ask: "Where did we lack Courage?" or "When did we fail to show Respect?" This makes values tangible. One team I read about used a "values thermometer"—a visual scale where each member rated how well the team lived each value during the sprint. The discussion that followed uncovered patterns: low Courage scores often correlated with unaddressed technical debt. The team then created an action item to allocate 10% of each sprint to debt reduction.

Tools and Techniques for Sustaining Values

Values Charter and Visual Reminders

Create a one-page values charter that defines each value with 2-3 observable behaviors. Display it prominently in the team's physical or virtual space. Some teams use a "value of the sprint" rotation—each sprint, they focus on one value and track related metrics. For example, during a "Focus" sprint, they measure the number of context switches per day and aim to reduce it by 20%. Tools like Miro or Trello can host a values board where team members post examples of values in action.

Regular Values Retrospectives

Every 4-6 sprints, dedicate a full retrospective to values alone. Use a technique like the "Values Star"—each team member draws a star with five points (one per value) and rates each from 1 to 5. The team then discusses discrepancies and creates improvement experiments. This prevents values from being forgotten in the rush of delivery.

Pairing Values with Agile Metrics

Metrics can reinforce values if used carefully. For example, track "sprint goal success rate" as a proxy for Commitment. Monitor "cycle time" as a proxy for Focus. Use "defect escape rate" to gauge Respect for quality. But avoid turning metrics into targets—they are diagnostic, not punitive. A team that sees a drop in sprint goal success might investigate whether they overcommitted (Commitment) or lacked Courage to push back.

Common Pitfalls and How to Avoid Them

Pitfall 1: Treating Values as Posters

Many organizations print values on posters but never discuss them. This creates cynicism. To avoid this, integrate values into every ceremony. If a value is violated (e.g., a team member is interrupted during a stand-up), address it immediately in a respectful way. The Scrum Master should model the values consistently.

Pitfall 2: Overemphasizing One Value at the Expense of Others

For example, too much Focus can lead to tunnel vision, ignoring the need for Openness to new ideas. A team might become so committed to a sprint goal that they resist necessary changes. Balance is key. Use the values as a system—each value supports the others. When one is weak, the whole system suffers.

Pitfall 3: Ignoring Organizational Culture Mismatch

If the larger organization rewards individual heroics or blames failure, a Scrum team's values will be under constant pressure. In such cases, the team can only control its own micro-culture. They can still practice Courage by pushing back on unreasonable demands, but they should also seek allies in management. Sometimes, the team's adherence to values becomes a quiet example that influences the wider organization over time.

Frequently Asked Questions About Scrum Values

How do we handle a team member who consistently violates a value?

Address it privately and constructively. Start with observation: "I noticed during the stand-up you interrupted several times. How can we support you in listening more?" Use the values charter as a neutral reference. If the behavior persists, escalate to the team in a retrospective, focusing on impact rather than blame. The goal is coaching, not punishment.

Can values be measured?

Indirectly. You can measure behaviors that reflect values, such as the number of impediments raised per sprint (Courage) or the percentage of sprint goals met (Commitment). But the core of values is qualitative. Use surveys (e.g., "On a scale of 1-5, how open was our team this sprint?") to track trends over time. The discussion around the scores is more valuable than the numbers.

What if the product owner doesn't respect the team's Focus?

This is a common challenge. The Scrum Master should coach the product owner on the value of Focus for long-term velocity. Use data: show how context switching reduces throughput. If the product owner continues to push, the team may need to escalate to management or accept that the sprint goal may be at risk. In extreme cases, the team can document the impact and present it during the sprint review.

Do values change as the team matures?

Yes. A new team might need to emphasize Respect and Openness to build trust. A mature team might focus on Courage to tackle harder challenges. Revisit the values charter every quarter and adjust the emphasis. The core values remain the same, but their expression evolves.

Synthesis and Next Steps

Assess Your Team's Current State

Start with a simple exercise: in your next retrospective, ask each member to rate the team on each value (1-5). Calculate the average and identify the lowest value. Discuss one small experiment to improve that value in the next sprint. For example, if Openness is low, try a "fail of the day" sharing at stand-up.

Create a Values Action Plan

For each value, define one concrete behavior to practice. Write it down and review it in the daily stand-up. Example: for Courage, "I will speak up if I see a risk before the end of the day." After a sprint, evaluate whether the behavior became a habit. If not, adjust.

Share Your Journey

Values spread through storytelling. In sprint reviews, share how a value helped the team overcome a challenge. This not only reinforces the value internally but also educates stakeholders. Over time, the team's reputation for integrity and collaboration will attract better opportunities and trust.