Table of Contents
ToggleIntroduction
You’re in the right place if you’ve ever wondered what are scrum values and why they’re important outside of frameworks and ceremonies. Scrum is more than just stand-ups, sprints, and backlogs. It is based on a solid set of common values that direct team conduct and choices.
In real agile transformations, we have noticed something consistent:
The teams adopt Scrum events quickly but struggle with the values underneath. Stand-ups happen. Boards are updated. Retrospectives are scheduled. Yet trust is low. Accountability is blurred. Difficult conversations are avoided.
That gap is not about framework knowledge. It’s about behavior that is lived by the team.
Scrum values are not abstract ideals. They show up in how teams respond under pressure.
The following five principles outline how Agile teams work together, adapt to change, and continuously produce value. We will look at what Scrum values are in Agile, how they relate to Agile principles, and how to incorporate them in real projects in this guide.
What Are Scrum Values?
Scrum values are the five core behavioral principles that support the Scrum framework. They were formally defined in the Scrum Guide, which highlights them as essential for successful Scrum implementation.
The five Scrum values are:
- Commitment
- Courage
- Focus
- Openness
- Respect
So when people ask what are 5 Scrum values, the answer is simple: these five guide how Scrum teams work together and deliver value.
They strengthen:
- Transparency
- Trust
- Accountability
- Collaboration
Without these values, Scrum events become mechanical rituals rather than meaningful collaboration tools.
You can run every ceremony perfectly and still miss agility. We have seen teams with flawless Jira boards and zero psychological safety.
Values determine whether Scrum is compliance-driven or outcome-driven.
Always remember that process enables & values transform.
The 5 Scrum Values Explained
Let’s break down the scrum values explained with definitions, examples, and team impact. These values are most visible when deadlines tighten, scope shifts, or stakeholders escalate. Calm periods don’t test values, it’s the pressure that does.
1. Commitment
Definition:
Scrum values commitment means the team commits to achieving its Sprint Goal and delivering high-quality work. It does not mean overpromising it means shared accountability.
Example:
A development team agrees on a realistic Sprint Goal during Sprint Planning and works collectively to achieve it, even if obstacles arise.
Impact on Teams:
- Builds ownership
- Encourages accountability
- Improves predictability
Commitment in Scrum is about commitment to goals, quality, and continuous improvement—not blind obligation.
2. Courage
Definition:
Courage means doing the right thing and addressing tough challenges openly.
Example:
A developer raises a concern that a feature may not meet quality standards even if it delays delivery.
Impact on Teams:
- Encourages transparency
- Supports innovation
- Reduces hidden risks
Courage ensures problems surface early, enabling better decision-making.
3. Focus
Definition:
Focus means concentrating on the Sprint Goal and avoiding distractions.
Example:
During a sprint, the team avoids adding new unplanned tasks unless absolutely necessary.
Impact on Teams:
- Increases productivity
- Reduces multitasking
- Enhances delivery speed
Focus aligns team energy toward delivering incremental value consistently.
4. Openness
Definition:
Openness means being transparent about progress, challenges, and feedback.
Example:
In Daily Stand-ups, team members honestly share blockers instead of hiding delays.
Impact on Teams:
- Builds trust
- Strengthens collaboration
- Enables faster issue resolution
Openness supports transparency, one of Scrum’s three pillars (Transparency, Inspection, Adaptation).
5. Respect
Definition:
Scrum value respect emphasises valuing each team member’s skills, perspectives, and contributions.
Example:
Product Owners respect developers’ technical insights; developers respect business priorities.
Impact on Teams:
- Reduces conflict
- Improves morale
- Strengthens collaboration
Respect creates psychological safety, which is critical for innovation.
Why Scrum Values Matter in Agile Teams?
Teams can go beyond process compliance when they understand the significance of Scrum values. Teams that internalize Scrum values typically demonstrate:
- Fewer last-minute surprises
- More realistic sprint commitments
- Faster conflict resolution
- Higher stakeholder trust
It happens because they communicate better and are not just following rules.
Scrum values in agile environments:
- Boost team confidence
- Improve communication
- Encourage shared accountability
- Facilitate quicker adaptation
Despite using Agile tools, many teams struggle because they fail to consider behavioral foundations. When values, not just frameworks, influence decisions, true agility is revealed.
When talking about what Scrum values and principles are, it’s crucial to realize that values have an impact on how Scrum principles are applied on a daily basis.
Scrum Values vs. Agile Principles
Many people confuse Scrum values with Agile values or Scrum principles. Let’s clarify the difference.
| Scrum Values | Agile Values | Scrum Principles |
| Behavioral foundation for Scrum teams | Defined in the Agile Manifesto | Guidelines that support Scrum framework |
| 5 specific values | 4 core values | Derived from empirical process control |
| Team-focused | Philosophy-focused | Framework-focused |
Think of it this way:
- Agile values shape how organizations think
- Scrum principles structure how Scrum works
- Scrum values shape how teams behave
The Agile Manifesto defines Agile values such as:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
Scrum values operate within that philosophy but apply specifically to Scrum teams.
In short:
- Agile values = philosophy
- Scrum principles = framework mechanics
- Scrum values = behavioral foundation
Values become real only when they influence daily micro-decisions:
- Do we raise this risk now or later?
- Do we accept lower quality to hit a date?
- Do we listen fully or defend our position?
Scrum values are rarely tested in theory.
They’re tested in moments.
Applying Scrum Values in Real Projects
Scrum values become meaningful when applied in everyday Scrum events.
1. Daily Stand-ups
Commitment: Team members commit to daily progress.
Openness: Blockers are shared honestly.
Focus: Discussions stay aligned with Sprint Goal.
Respect: Everyone listens without interruption.
Courage: Issues are raised early.
Result: Improved transparency and faster problem resolution.
2. Sprint Planning
Commitment: The team agrees on a realistic Sprint Goal.
Focus: Prioritized backlog items are selected carefully.
Respect: Product Owner and Developers collaborate equally.
Courage: Capacity concerns are voiced openly.
Openness: Scope discussions are transparent.
Result: Predictable and achievable sprint outcomes.
3. Retrospectives
Openness: Honest feedback about what went wrong.
Respect: No blame culture.
Courage: Difficult conversations happen constructively.
Commitment: Team commits to improvement actions.
Focus: Improvements are aligned with measurable outcomes.
Result: Continuous improvement and stronger team cohesion.
Common Misconceptions About Scrum Values
“Scrum values are just soft skills.”
We have heard this many times in workshops.
But here is what usually follows in struggling teams:
- Missed sprint goals
- Hidden blockers
- Quiet resentment, and
- Reactive firefighting
Values directly affect delivery predictability. We believe the Agile COE of any organization should paste this near the walls where the teams are working or use it as banner on the desktops that:
When courage is missing, risks stay hidden – When focus is weak, sprint goals drift.
“Values are optional as long as we follow the process.”
Mechanical Scrum will surely lead to failure. Value is the north star.
We have seen teams run perfect ceremonies while avoiding uncomfortable truths. The board looks clean. The increment looks delayed.
Events don’t create honesty. People do.
“Scrum values are the same as company values.”
Not necessarily. Company values define broad culture. Scrum values define how a small delivery team behaves day to day.
You might work in an organization that promotes “innovation” but if a developer is afraid to question a rushed release, courage isn’t present in practice.
“If we run ceremonies, values will naturally emerge.”
They don’t automatically. Starting from top, the leaders should enforce the abidement of values over practices. Followed by
- Openness by Scrum Masters
- Respect by Product Owners
- Reinforcing commitment through realistic planning by teams.
Ceremonies provide structure. Values give them meaning.
Conclusion
So, what are Scrum values? They are the behavioral backbone of successful Scrum teams.
The 5 Scrum values: Commitment, Courage, Focus, Openness, and Respect create trust, improve collaboration, and strengthen Agile execution. Without them, Scrum becomes a checklist; with them, it becomes transformative.
In 2026 and beyond, high-performing Agile teams will embody these values in every interaction, decision, and delivery cycle.
The highest-performing Scrum teams we have worked with don’t talk about values frequently. They demonstrate them consistently.
You see it in
- How they plan realistically
- How they challenge assumptions respectfully
- How they surface risks early
- How they learn without blame
As an agile consulting company which has curated and implemented more than 20 agile transformation journeys, we believe Scrum values are not theoretical. They are observable. And when they are present, performance follows.. Are you struggling with getting value even after scrum adoption? NextAgile consulting can help you co‑create and implement a practical scrum adoption roadmap. Do reach out to us at consult@nextagile.ai and we would be happy to explore more.
Frequently Asked Questions
1. What are Scrum values in simple terms?
They are five shared behaviors that guide how a Scrum team works together.
Commitment, Courage, Focus, Openness, and Respect
If you stripped Scrum of its boards and ceremonies, these five behaviors would still define whether a team succeeds.
2. How do Scrum values differ from Scrum roles?
Roles define who does what.
Values define how people behave while doing it.
You can have a Product Owner, Scrum Master, and Developers clearly defined but if respect or openness is missing, collaboration breaks down quickly.
3. Can Scrum values improve remote team collaboration?
Absolutely. In distributed teams, informal check-ins help but can not be fully relied upon as it may provide the gap for assumptions or deeper enquiry. Openness and commitment become even more critical. One common observation: when someone says, “Everything’s fine,” but avoids mentioning blockers, distance magnifies the problem.
Remote teams succeed when transparency is intentional and trust plays a detrimental role.
4. What are Scrum values vs company values?
Company values describe the broader organizational culture. Scrum values operate at the team level like inside sprint cycles, planning discussions, retrospectives, and delivery tradeoffs.
Anuj Ojha
Anuj Ojha is Co-Founder & Consulting Head at NextAgile. Anuj has designed & led multiple turnkey transformation journeys across industries, domains & geographies and has 16+ years of experience as an agile practitioner. He has worked with CXOs, CTOs & Key Leaders to translate their business objectives on the ground, contextualizing org transformations and creating buy-in across level, leading a team of coaches/consultants to implement agility across 150+ teams & trained more than 12k team members. Anuj’s core area of interest is business agility & working with leaders & teams to achieve long term sustainable, Agile culture & mindset.


