The Scrum Guide describes five values: Courage, Focus, Commitment, Respect, and Openness. They appear in the document before the roles, the events, or the artefacts — which is deliberate. The values are the soil the framework grows in. Without them, Scrum becomes a set of rituals that produces the appearance of agility without any of the substance.

Courage

Scrum requires courage in a specific and demanding sense: the willingness to surface difficult truths in real time. To say in a Sprint Review that the increment does not actually meet user needs. To raise an impediment in a Daily Scrum that reflects a deeper problem with how the team is working. To tell the Product Owner that the estimates were wrong and the Sprint Goal is at risk.

The obstacle to this kind of courage is usually not personal timidity — it is the absence of safety. Teams that operate in environments where bad news is punished rather than welcomed quickly learn to manage information rather than share it. Building a culture where courage is possible means building a culture where honest communication is genuinely valued, including when the message is inconvenient.

Focus

Focus in Scrum means that during a Sprint, the team's energy is directed toward the Sprint Goal — not toward the seventeen other interesting things that could be worked on, not toward requests that arrive after Sprint Planning, not toward long-running side projects that compete for attention.

This is harder than it sounds in organisations where demands are continuous and boundaries are culturally weak. The discipline of focus is part of what makes Scrum productive — and part of what makes adopting it uncomfortable in environments where everything has always been treated as equally urgent. Protecting the Sprint is a team responsibility, not just the Scrum Master's job.

Commitment

The Scrum Guide is careful about this value. Commitment in Scrum is not a promise to deliver specific features by a specific date — it is a commitment to the Sprint Goal and to the team. The distinction matters because commitment to arbitrary promises tends to produce bad behaviour: cutting corners, hiding problems, working unsustainable hours to ship something that should not have been shipped.

Commitment to the team and the goal looks different. It means taking ownership of outcomes rather than just tasks. It means raising blockers early rather than discovering them on the last day of the Sprint. It means showing up to events prepared, because the other members of the team are depending on your contribution.

Respect

Scrum teams are self-organising. This only works if the members of the team genuinely respect each other's expertise, perspectives, and contributions. The developer who questions a requirement is not being obstructive — they may be surfacing a problem that saves significant rework. The Scrum Master who pushes back on a stakeholder request during the Sprint is not being unhelpful — they are protecting the team's ability to deliver what they committed to.

Respect also extends to difference of opinion. The Scrum ceremonies are designed in part to create space for constructive disagreement — the kind that improves decisions rather than the kind that produces resentment. Getting this right requires both structural support and individual discipline.

Openness

Transparency is a pillar of Scrum, and openness is what makes transparency possible. Teams that are open about their progress, their impediments, and their doubts allow problems to surface at a scale where they can be addressed. Teams that manage information tend to surface problems at a scale where they cannot.

Openness also applies to improvement. The Sprint Retrospective is premised on the assumption that the team is willing to examine its own practices honestly and change what is not working. Teams that enter retrospectives with the implicit agenda of confirming that everything is fine are not practising openness — they are practising performance.

The five values reinforce each other. Courage without respect produces aggression. Focus without commitment produces distraction. Openness without psychological safety produces silence. Together, they create the conditions for Scrum to function as intended — not as a compliance exercise, but as a genuine system for delivering value and continuously improving.