The Five Scrum Values in Real Teams: Commitment, Focus, Openness, Respect and Courage
Many people learn Scrum as a list of events and artifacts and never notice that the Scrum Guide also names five values: Commitment, Focus, Openness, Respect and Courage. The guide says that successful use of Scrum depends on people becoming more proficient in living these values. In other words, the mechanics only work when the culture underneath them is healthy. This lesson explains each value in practical terms and shows what it looks like, and what its absence looks like, in a real team.
Why Values Matter More Than Mechanics
Scrum is deliberately incomplete. It does not tell a team how to design software, how to handle a conflict or what to do when a Sprint goes badly. The values fill that gap. When the framework is silent, the team asks: what would a team that values commitment, focus, openness, respect and courage do here? If you have read about the Agile Manifesto, you will recognise the same idea: shared principles guide behaviour where rules run out.
1. Commitment
Meaning: People personally commit to achieving the goals of the Scrum Team and to supporting each other. In the 2020 Scrum Guide each artifact has an associated commitment: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment.
What it looks like: Developers care whether the Sprint Goal is met, not just whether their own tickets are closed. When someone is stuck, others offer help without being asked.
Warning signs: "That's not my task." Stories left at 90% for days. The Definition of Done quietly ignored when a deadline looms.
2. Focus
Meaning: Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
What it looks like: A clear Sprint Goal that guides daily decisions. Few items in progress at once. New requests are routed through the Product Owner rather than injected mid-Sprint.
Warning signs: Developers working on six items at once, constant context switching, people pulled onto unplanned work by managers, Sprint Goals that read like a list of unrelated tickets. See Sprint Goal Problems.
3. Openness
Meaning: The Scrum Team and stakeholders are open about all the work and the challenges with performing the work.
What it looks like: A visible board that reflects reality, honest statements at the Daily Scrum such as "I'm blocked" or "I underestimated this", and unflattering metrics shared openly rather than hidden.
Warning signs: Status updates that are always green, problems discovered at the Sprint Review for the first time, team members who say "fine" in meetings and complain afterwards. Openness depends on psychological safety; see Psychological Safety in Scrum Teams.
4. Respect
Meaning: Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work.
What it looks like: Listening without interrupting, disagreement about ideas without attacks on people, trusting Developers to decide how to do the work, and trusting the Product Owner to order the backlog.
Warning signs: Sarcasm in retrospectives, managers overruling team estimates, one voice dominating discussions, blame language ("QA missed it").
5. Courage
Meaning: Scrum Team members have the courage to do the right thing and work on tough problems.
What it looks like: Saying "we cannot commit to that scope", challenging a stakeholder who wants everything by Friday, raising a quality concern even when it is unpopular, or deciding to stop a failing experiment.
Warning signs: Teams that always say yes, known problems nobody raises, a Scrum Master who avoids hard conversations with management to stay comfortable.
How the Values Reinforce Each Other
The values form a system. Openness without respect becomes blame. Courage without respect becomes aggression. Commitment without focus becomes busyness. Focus without openness hides problems until they are big. When a team struggles, it is useful to ask which value is weakest, because strengthening it often unblocks the others.
Values in Action: A Short Scenario
Midway through a Sprint, a senior stakeholder asks a Developer to "quickly" add a feature. The Developer is tempted to say yes to avoid conflict.
- Courage lets the Developer say, "I'll check with the Product Owner."
- Focus reminds the team of the Sprint Goal.
- Openness means the request is raised at the Daily Scrum rather than absorbed silently.
- Respect means the stakeholder's need is heard and taken seriously, even if it is scheduled for a later Sprint.
- Commitment means the team protects the goal they agreed to.
How a Scrum Master Nurtures the Values
- Model them. Admit your own mistakes (openness), protect the team from interruptions (focus), and have the difficult conversations (courage).
- Name them in retrospectives. Ask, "Which value did we live well this Sprint? Which one did we struggle with?"
- Use working agreements. Turn each value into two or three concrete behaviours the team writes down and reviews.
- Notice and reinforce. When someone shows courage, acknowledge it publicly.
- Remove fear. If people are punished for bad news, openness will disappear no matter how many posters you hang.
Interview Tip
A frequent interview question is, "Which Scrum value do you think is most important, and why?" There is no single right answer. A strong response picks one, ties it to a real situation, and acknowledges the interplay with the others. See Scrum Master Scenario Interview Questions for more practice.
- The five values are Commitment, Focus, Openness, Respect and Courage.
- They guide behaviour where the framework gives no explicit rule.
- They reinforce each other; weakness in one weakens the rest.
- Scrum Masters nurture them by modelling, naming and removing fear.