TLDR
The five Scrum values are commitment, courage, focus, openness, and respect. They matter more than any ceremony or artifact because they shape how your team actually behaves when things get hard. Teams that memorise the values but don’t practise them end up doing Scrum-flavoured waterfall.
This post breaks down each value with real examples, the anti-patterns that show a value is missing, and practical ways to make these values visible in your team’s daily work.
Your Team Knows the Ceremonies but Something Still Feels Off
The standups happen. The retros are on the calendar. Sprint Planning runs every two weeks like clockwork. But the team still hides problems until they blow up. People commit to work they know they can’t finish. Nobody pushes back on unrealistic deadlines from stakeholders.
The ceremonies are there, but the foundation underneath them is cracked. That foundation is the five Scrum values. Without them, you’re running a process. With them, you’re building a team that actually works.
Why Values Matter More Than Ceremonies
The Scrum Guide dedicates an entire section to values, and there’s a reason for that. Ceremonies give you structure. Values give you behaviour. You can follow every ceremony perfectly and still have a dysfunctional team if the values aren’t there.
Think about it this way: Sprint Planning without commitment means the team agrees to things they won’t actually deliver. A retrospective without openness means people smile and say “everything’s fine” while problems fester. A Daily Scrum without courage means blockers go unmentioned.
Values are what make the ceremonies actually work. They’re the difference between going through the motions and genuinely improving sprint after sprint.
Commitment: Doing What You Said You’d Do
Commitment in Scrum doesn’t mean promising to hit an arbitrary deadline someone else picked. It means the team genuinely dedicates itself to achieving the Sprint Goal and supporting each other along the way.
What Commitment Looks Like in Practice
A committed team pulls work they believe they can finish. When they realise mid-sprint that they overcommitted, they talk about it immediately instead of silently working weekends. They protect the Sprint Goal by saying no to scope creep that doesn’t serve it.
Commitment also shows up in the small things. Showing up to ceremonies on time. Finishing what you started before picking up new work. Following through when you say “I’ll look into that.”
Anti-Patterns That Signal Missing Commitment
Overcommitting every sprint. If your team consistently takes on more than they can finish, that’s not ambition. It’s a lack of honest commitment. The velocity charts don’t lie.
Cherry-picking easy tickets. When team members grab the simple work and leave the hard stuff for someone else, individual comfort is winning over team commitment.
“That’s not my job.” Scrum teams commit to a Sprint Goal together. When someone refuses to help because a task falls outside their usual role, commitment has broken down.
Courage: Saying the Hard Thing
Courage is the value that makes all the others possible. Without it, commitment becomes people-pleasing. Openness becomes superficial. Respect becomes avoidance.
What Courage Looks Like in Practice
A developer tells the Product Owner that the “quick fix” they want will create technical debt that slows the team down for months. A Scrum Master raises a concern about team burnout even when leadership doesn’t want to hear it. A team member admits they’re stuck on a problem instead of struggling alone for three days.
Courage also means being willing to try new approaches. Running experiments. Changing how you estimate if the current way isn’t working. Killing a feature mid-sprint because the data says it’s the wrong direction.
Anti-Patterns That Signal Missing Courage
Silent standups. Everyone says “same as yesterday, no blockers” even when blockers exist. People are afraid of looking incompetent.
Retro theatre. The retro surfaces only safe, minor issues like “we should update the wiki more” while the real problems (unclear requirements, absent Product Owner, impossible deadlines) go unspoken.
Saying yes to everything. When leadership says “just add this one thing to the sprint,” the team agrees without discussing the impact. Nobody wants to be the person who pushes back.
Focus: Doing Fewer Things Better
Scrum’s entire structure is designed around focus. The sprint creates a time boundary. The Sprint Goal creates a purpose boundary. The Sprint Backlog creates a work boundary. All of this exists so the team can concentrate on a small set of things and actually finish them.
What Focus Looks Like in Practice
A focused team has a clear Sprint Goal that everyone can articulate without checking Jira. They limit their work in progress so nothing sits half-done for days. They protect their sprint from interruptions and context-switching whenever possible.
Focus also means the Product Owner keeps the backlog sharp. Low-priority items don’t clutter the top. The next sprint’s work is refined and ready. The team isn’t guessing about what matters most.
Anti-Patterns That Signal Missing Focus
Vague or missing Sprint Goals. If the Sprint Goal is “complete the sprint backlog” or it doesn’t exist at all, there’s nothing to focus on. The team is just working through a task list.
Everyone has five things in progress. High WIP is the enemy of focus. When a team of five has 15 items in progress, nothing is getting finished.
Constant interruptions. Support tickets, urgent requests, and “quick questions” fragment the team’s attention. If this happens every sprint, it’s a systemic problem, not bad luck.
Openness: Showing Your Work, Even When It’s Messy
Openness means being transparent about progress, problems, and what you’re learning. It’s the value that makes inspect-and-adapt actually work. Without openness, your sprint reviews show a polished demo while hiding the chaos underneath.
What Openness Looks Like in Practice
The burndown chart is visible and accurate, not massaged to look good. When a story turns out to be twice as complex as estimated, the team surfaces that immediately. Sprint Reviews show what was actually built, including the parts that didn’t go as planned.
Openness between the team and stakeholders matters too. If the roadmap is at risk, say so early. If a dependency is going to cause a delay, flag it now rather than hoping it resolves itself.
Anti-Patterns That Signal Missing Openness
Hidden work. People do tasks that aren’t on the board. The board says everything is green, but the team is drowning.
Sandbagging estimates. The team pads every estimate with a massive buffer because they’ve been punished for missing targets before. The lack of trust kills transparency in both directions.
Blame culture. When something goes wrong and the first question is “whose fault was this?” people learn to hide problems. Openness dies fast in a blame culture.
Respect: Treating Each Other as Capable Adults
Respect in Scrum means trusting that your teammates are competent and well-intentioned. It means valuing different perspectives and recognising that the person closest to the work usually has the best insight into how to do it.
What Respect Looks Like in Practice
A respectful team lets the developers decide how to do the work. The Product Owner decides what to build, but doesn’t micromanage the implementation. Team members listen to each other in standups instead of checking Slack on their phones.
Respect also means respecting the process. Showing up to ceremonies prepared. Not cancelling the retro because “we’re too busy.” Acknowledging that everyone’s time matters.
Anti-Patterns That Signal Missing Respect
Micromanagement from outside the team. When managers assign individual tasks, override estimates, or dictate how the work should be done, they’re signalling they don’t trust the team.
Talking over each other. If one or two voices dominate every meeting and quieter team members never speak up, respect for diverse perspectives is missing.
Dismissing expertise. “You’re just a tester, why do you have an opinion on architecture?” That kind of comment poisons a team fast. Everyone on the Scrum Team has a perspective worth hearing.
How to Make the Scrum Values Visible
Values that live on a poster and nowhere else are useless. Here are ways to make them part of your team’s daily behaviour.
Reference Values in Retros
Try running a retro format where the team evaluates the sprint through the lens of each value. “How well did we live commitment this sprint? Where did we show courage? Where didn’t we?” This connects abstract values to concrete behaviour.
Build Values Into Working Agreements
Instead of generic working agreements like “be on time,” tie them to values. “We show commitment by flagging blockers within 24 hours.” “We show courage by raising scope concerns during Sprint Planning, not after.” This makes the values actionable.
Call Them Out in Real Time
When someone demonstrates a value, name it. “Thanks for flagging that risk early. That took real courage.” When a value is being violated, name that too, but do it with respect. “We committed to this Sprint Goal together. Taking on this new request would put it at risk.”
Use a Values Health Check
Once a quarter, have each team member rate how well the team is living each value on a scale of 1 to 5. Discuss the results. Look for gaps between how different people perceive the same value. Those gaps are where the real conversations happen.
Values and the Scrum Guide
The 2020 Scrum Guide made the values more prominent than any previous version. They’re not optional flavour text. The Guide states explicitly: “When these values are embodied by the Scrum Team and the people they work with, the empirical Scrum pillars of transparency, inspection, and adaptation come to life building trust.”
The three pillars of empiricism (transparency, inspection, adaptation) depend on the values. You can’t have transparency without openness. You can’t inspect honestly without courage. You can’t adapt without commitment to trying something new.
If your team is struggling with Scrum, before you change any process, ask which values are weak. The answer usually points you toward the real problem.
Frequently Asked Questions
The five Scrum values are commitment, courage, focus, openness, and respect. They were formally added to the Scrum Guide in 2016 and given even more prominence in the 2020 update. These values guide how team members interact with each other and approach their work within the Scrum framework.
The Scrum values are important because they underpin the three pillars of empiricism: transparency, inspection, and adaptation. Without values like openness and courage, teams can’t be transparent about problems. Without commitment, adaptation becomes hollow. The values determine whether Scrum ceremonies produce real improvement or become empty rituals.
Don’t lecture about them. Instead, introduce them during team formation and then reference them in daily work. Use retros to discuss which values showed up during the sprint. Create working agreements tied to specific values. Model the values yourself. Teams learn values by seeing them in action, not by reading a poster.
The Agile Manifesto has four values (individuals and interactions, working software, customer collaboration, responding to change) and 12 principles. The five Scrum values (commitment, courage, focus, openness, respect) are specific to the Scrum framework. They’re complementary. Agile values describe a mindset. Scrum values describe team behaviours within that mindset.
The three Scrum pillars are transparency, inspection, and adaptation. The values make the pillars possible. Openness enables transparency. Courage and respect enable honest inspection. Commitment and focus enable meaningful adaptation. Without the values, the pillars collapse and Scrum becomes process theatre.
Absolutely. Commitment, courage, focus, openness, and respect are solid team values regardless of your framework. Kanban teams, XP teams, and non-Agile teams all benefit from these behaviours. The values aren’t locked behind a Scrum certification. They describe how high-performing teams operate in general.
This is common and uncomfortable. If the company culture punishes failure, courage and openness will struggle. If management micromanages, respect and commitment suffer. The answer isn’t to abandon the values. It’s to use the tension as a signal that organisational change is needed. Start with the team, demonstrate better results, and use those results to influence the wider culture.
Run periodic values health checks where each team member rates the team on each value (1 to 5). Look at behavioural indicators: Are blockers raised quickly (courage, openness)? Does the team protect the Sprint Goal (commitment, focus)? Do all voices get heard in meetings (respect)? The trends matter more than the absolute numbers.
Get Practical Agile Insights Every Week
Techniques like these, delivered to your inbox. No certification fluff, no buzzwords. Just what actually works in real teams.
Subscribe
Leave a Comment