Scrum Values
Scrum rests on five values: Commitment, Courage, Focus, Openness, and Respect. Rules and events give Scrum its shape, and the values give it life. A team that lives these values makes better decisions without waiting for instructions.
Why Values Matter
Scrum uses short cycles and frequent inspection. Inspection only works when people report the truth. Adaptation only works when people dare to change course. The five values create the trust that makes honest reporting and bold change possible.
Empirical Process Control
Transparency · Inspection · Adaptation
┌────────────────────────────────────┐
│ Commitment Courage Focus │
│ Openness Respect │
└────────────────────────────────────┘
Scrum Team Trust
The Five Values
Commitment
Team members commit to achieving the Sprint Goal and to supporting each other. Commitment means dedication to a shared outcome and never a promise to finish every single task regardless of reality. The Definition of Done gives the Developers a clear commitment to quality.
Courage
Scrum Team members dare to do the right thing and to tackle tough problems. A developer raises a design flaw even when the deadline looms. A Product Owner removes a favorite feature that no longer serves users.
Focus
Everyone concentrates on the work of the Sprint and the goals of the team. Focus protects the team from side requests and endless multitasking. One goal at a time produces finished work faster than ten goals at once.
Openness
The team and its stakeholders share the work and the challenges openly. Boards stay visible, progress stays honest, and problems appear on the table early. Hidden problems grow, and open problems shrink.
Respect
Team members respect each other as capable, independent people. Stakeholders respect the team's decisions about how to build. Respect creates an environment where disagreement stays productive.
Values in Action: Library App Team
A team builds a mobile app for a city library. Midway through the Sprint, a developer discovers that the book-search feature slows down badly for large catalogs. The table shows how the values guide the response.
| Moment | Value Shown | Behavior |
|---|---|---|
| Developer reports the slowdown in the Daily Scrum | Openness | Shares the problem on day four instead of hiding it |
| Developer proposes dropping a lower-priority feature | Courage | Suggests a hard tradeoff in front of everyone |
| Team pauses new tasks to fix the slowdown together | Focus | Concentrates on the Sprint Goal |
| Product Owner listens to the technical reasons | Respect | Trusts the expertise of the Developers |
| Everyone stays until the Sprint Goal is met | Commitment | Supports each other toward the shared result |
When Values Break Down
Weak values leave visible symptoms. Developers stay silent in meetings. The board shows green while the product shows red. Managers interrupt the Sprint with new requests. People blame individuals after a failure.
- Low openness produces surprise problems on the last day of a Sprint.
- Low courage produces features nobody wants.
- Low focus produces many half-finished items.
- Low respect produces conflict and turnover.
- Low commitment produces missed goals and shrugged shoulders.
Ways to Strengthen the Values
- Write the five values on the team wall and discuss one in each Retrospective.
- Ask team members to share one honest concern in every Daily Scrum.
- Thank people who raise bad news early.
- Limit work in progress so focus becomes natural.
- Invite stakeholders to every Sprint Review and listen without defending.
Values grow through repeated behavior. Every honest report, every respectful disagreement, and every protected hour of focus adds to the team's trust. Strong trust turns Scrum events from rituals into useful conversations.