Empiricism and Scrum values · Lesson 4

Five Scrum values in a difficult decision

8 min read

Lesson objectives

  • The learner explains how commitment, focus, openness, respect and courage shape a disputed Sprint decision without treating the values as slogans.
Reading tools

Five Scrum values in a difficult decision

Three days before a Sprint ends, a team discovers that a notification feature sends duplicate messages to some customers. A stakeholder wants it released on the announced date. A Developer hesitates to report the defect because management criticized an earlier delay. Knowing the names of Scrum's five values is not enough here. The useful question is how they shape the team's behavior and decision. Commitment means commitment to goals and to supporting one another, not a promise that every item forecast at planning must be delivered regardless of new evidence. Focus directs effort to Sprint work that makes the best progress toward its goal, rather than opening new items to make a dashboard look busy.

Openness calls for making the defect and its effect clear instead of hiding it until the final presentation. It does not require flooding everyone with technical detail. Give decision makers the relevant facts: when do messages repeat, who is affected and does the Increment meet the Definition of Done? Respect means hearing both the stakeholder's concern about the date and the Developer's knowledge of the risk, treating each person as capable of contributing. Courage appears when a team member reports uncomfortable evidence, when the Product Owner revises an expectation in light of the product's actual condition, and when the organization supports that candor rather than punishing it.

The values can appear to pull in different directions: do we honor the date or speak openly about the defect? Resolve the tension by identifying what the team actually committed to. The Sprint Goal and quality agreement do not authorize duplicate customer messages. If the defect can be fixed within the time and to the agreed quality, Developers can focus on that work and adapt their plan. If it cannot, they do not label unfinished work a usable Increment. The Product Owner explains the impact and alternatives to stakeholders, perhaps releasing another Done piece if it has value and meets its criteria. Values do not grant anyone a new authority outside their accountability; they guide how accountabilities are exercised.

To analyze a values situation, ask which truth is difficult to say, which goal deserves focus, whose perspective has not been heard, and whether commitment to a goal is being confused with obedience to a detailed plan. In the notification case, a sales leader might ask the team to conceal the defect until a campaign ends. Openness and courage favor disclosure; respect calls for explaining the commercial impact without dismissing it; focus directs effort to the work most relevant to the Sprint Goal; commitment calls for supporting the team in its decision rather than looking for someone to blame. This is not an equation with one numerical result. It is a way to choose behavior that sustains empiricism and trust.

Do not reduce the values to individual politeness. An organization can tell team members to be open and then punish those who raise a risk early; that environment undermines truthfulness. The Scrum Master helps the organization understand how incentives and decision channels affect Scrum's effectiveness. A Product Owner can respect Developers by not dictating implementation, while still discussing value and Product Backlog ordering. Developers respect one another when they inspect each other's work and maintain a shared Definition of Done. Values become visible in everyday consequences, not in a poster on a wall.

An assessment option saying ‘follow the stakeholder request immediately’ may sound cooperative, yet undermine transparency, quality and accountabilities. Another option saying ‘refuse any discussion because the team is independent’ may sound protective of self-management, yet close off respect and learning from affected people. Look for a response that makes facts visible, hears the parties and protects the Sprint Goal and quality, with the decision made by the relevant accountable people. Explain why. Memorizing the five names alone will not solve a situation with competing wishes and constraints.

Courage can begin with a small question from a new team member. If they notice that a success measure excludes difficult cases, first hear how they counted. Respect lets the information surface, openness supports inspection, and focus helps select action serving the Goal. Commitment includes following that action through to an observed result rather than merely praising the question. Describe the fact without judging the measure owner's motives, then request an example supporting or refuting exclusion. Recalculate while letting the colleague explain their original choice. This combines dignified interaction with professional rigor. If discussion shifts to job titles, bring it back to the effect of excluded cases on users. Exclusion may be legitimate when scope is explicit; the result's wording and applicable population must then reflect it. Learning from the challenge makes values observable behavior.

Lesson summary

The learner explains how commitment, focus, openness, respect and courage shape a disputed Sprint decision without treating the values as slogans.