A home-robot company's cloud team keeps context-switching mid-Sprint to help other teams with unrelated production incidents, leaving their own Sprint Goal at risk. Which Scrum value most directly addresses what the team is failing to uphold?
Select an answer to reveal the explanation.
Short Explanation
Helping other teams isn't the problem here — losing sight of your own Sprint Goal while doing it is. Focus is the value that says the primary attention stays on the Sprint's own work; constant context-switching away from it is exactly what Focus is meant to protect against.
Full Explanation
The Scrum Guide names Focus as one of the five Scrum values, describing it as everyone focusing primarily on the work of the Sprint and on achieving the goals of the Scrum Team. A team that repeatedly context-switches into unrelated production incidents, putting its own Sprint Goal at risk, is directly failing to uphold Focus, regardless of how well-intentioned the interruptions are. Openness is a separate value about being open about the work and the challenges faced — it would be relevant if the team hid the interruptions from the Product Owner or Scrum Master, but the scenario doesn't turn on concealment, it turns on divided attention. Courage covers doing the right thing and tackling hard problems, which doesn't map onto choosing to context-switch; if anything, courage might be what's needed to say no to the interruption in order to protect the Sprint Goal. Respect covers Scrum Team members treating each other as capable, independent people — it doesn't extend to justifying abandoning one's own Sprint commitments as an act of respect toward another team. A concrete check: when interruptions like this recur, look at whether the Sprint Goal is being explicitly renegotiated with the Product Owner, or just silently sacrificed — the latter is a Focus problem the Scrum Master should raise.