When Pressure Hits: What the Five Scrum Values Looked Like on a Hybrid Team
In the spring of 2021, a mid-sized agency we worked with was rebuilding a product team after a rough year. Two members had left, supply delays had pushed a hardware integration back twice, and half the team was still working from kitchen tables. The Scrum Master had the Scrum Guide's five values pinned to the team's virtual board — commitment, focus, openness, respect, and courage — and quietly worried they had become decoration. What follows is an anonymized look at how those values actually earned their place over one difficult quarter.
Scrum.org is clear that the five values are not a motivational slogan. They are the behaviours that make the empirical pillars — transparency, inspection, and adaptation — work in practice. A team can run every event on the calendar and still fail if people hide bad news or refuse to change course. The interesting part is how concrete the values become under real pressure.
The values, as they showed up
Commitment. Early on, the team over-promised in Sprint Planning to look productive, then quietly carried work over. The turning point was committing to a Sprint Goal they could actually defend, not a wish list. Commitment meant standing behind the goal and the Definition of Done, not behind an inflated forecast.
Focus. With people split across home and office, context-switching was the silent tax. The team agreed to one Sprint Goal at a time and stopped pulling "quick favours" from other departments mid-Sprint. Focus was a boundary, not a personality trait.
Openness. The hardware delay had been known for a week before anyone said it in a Daily Scrum. Once the Scrum Master made it safe to raise blockers without blame, problems surfaced days earlier — which is the whole point of inspection.
Respect. A newer developer kept proposing a simpler integration approach and kept getting talked over on video calls. Respect meant treating that suggestion as worth testing. It turned out to be the one that shipped.
Courage. Halfway through the quarter the Product Owner cancelled a feature the team had already started, because the market had moved. Courage was admitting the sunk cost out loud and adapting, rather than finishing something nobody needed.
Why the values matter more on a distributed team
Co-located teams get a lot of these values for free through hallway conversations and body language. Remote and hybrid teams have to make them deliberate. The agency learned to write blockers in a shared channel within the hour, to keep the Daily Scrum to fifteen focused minutes, and to confirm decisions in text so quieter voices were not lost on a laggy call. None of that is in the Scrum Guide word for word, but all of it is the five values made tangible for the way the team actually worked.
What we tell teams to try
Tie each Sprint to a single, defensible Sprint Goal — commitment you can point to.
Protect the Sprint from mid-stream requests; route them through the Product Owner — that is focus in action.
Make raising a blocker a sign of a healthy team, never a failure — that is how openness survives.
In a hybrid setting, give every idea a written hearing so the loudest channel does not win by default.
Reward the person who says "let's stop this" when the evidence has changed — that is courage worth keeping.
By the end of the quarter the team was not faster because it worked longer hours. It was steadier because the values turned events that had been routine into honest ones. That is the quiet promise of Scrum done well: the framework gives you the meetings, but the values give the meetings their teeth.
If your organization is standing up or recovering project teams and wants the practices to stick, XNM's program & project delivery advisory can help you build the habits behind the framework, not just the calendar.