Courage

How do we tackle tough problems?

I spoke up about a technical debt issue that everyone was avoiding
We had the courage to push back on unrealistic deadlines
I admitted my mistake in estimation and learned from it
Focus

How can we improve focus on our goals?

We reduced our WIP limit to maintain better focus
Daily stand-ups help me stay focused on sprint priorities
I block out 'do not disturb' time for deep work
Openness

How do we stay open to new things?

We've started sharing our learnings in weekly tech talks
I'm more open to pair programming after trying it
Our team board is visible to all stakeholders
Respect

How do we respect each other?

We value each team member's unique perspective in discussions
I appreciate how we respect different working styles
Our code review comments are always constructive
Commitment

How can we make our commitments a reality?

We're consistently delivering on our sprint commitments
I completed the training I promised to do last quarter
Our definition of done guides our quality commitment

What is the Scrum Values Retrospective?

The Scrum Values retrospective asks your team how well it lives the five values at the heart of Scrum: Courage, Focus, Openness, Respect and Commitment. You take each value in turn and look at how it shows up in daily work. Splitting them out makes the conversation concrete. Instead of asking whether the team is 'doing Scrum well', you're asking whether people speak up about problems, protect their focus time and follow through on what they agreed. The five values are set out in the Scrum Guide by Ken Schwaber and Jeff Sutherland. They're what make the events and artifacts work, because practices like daily stand-ups and retros depend on trust and honesty. This retrospective helps your team look past the mechanics of the process at how people actually work together.

Scrum Values Retrospective Format

Courage

How do we tackle tough problems?

Courage in Scrum means facing difficult situations and challenges head-on. Encourage participants to share instances where they've shown courage or where they feel the team needs more courage. Look for examples of speaking up, admitting mistakes, or taking calculated risks.

Focus

How can we improve focus on our goals?

Focus is the team's ability to concentrate on the current sprint work and project goals. Guide the discussion toward distractions and ways to stay focused. Consider focus challenges for individuals and for the team as a whole.

Openness

How do we stay open to new things?

Openness involves transparency about work, challenges, and opportunities for improvement. Encourage discussion about information sharing, willingness to try new approaches, and receptiveness to feedback. Look for ways to create a more open environment.

Respect

How do we respect each other?

Respect means acknowledging each team member's contributions and treating everyone as capable, independent people. Guide the discussion to explore how respect is shown (or could be improved) in daily interactions, decision-making, and collaboration.

Commitment

How can we make our commitments a reality?

Commitment in Scrum means dedicating yourself to team goals and continuous improvement. Focus the discussion on how well the team follows through on sprint commitments, process improvements, and personal development goals.

When to use this retrospective

  • When your team is new to Scrum and needs to understand the values in practice.
  • When team dynamics or performance problems suggest people have drifted from the values.
  • As part of a quarterly team health check, alongside your regular sprint retros.
  • Before a big change or a hard stretch that will test how the team works together.

Suggested icebreaker questions

  • Which Scrum value do you find easiest to practice and why?
  • Share a recent moment when you saw a teammate show one of these values.

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Ask for specific examples. They're easier to act on than general statements.
  • Have each person rate the team on each value and plot the results on a radar chart.
  • Make it safe to be honest. No team lives all five values perfectly, and saying so up front helps.
  • Try discussing one value a day in the run-up to the retro, so people arrive with examples.
  • Record a concrete action for each value so you can track progress.
  • Use real moments from recent sprints to show where a value was lived, or wasn't.

Frequently asked questions

What are the five Scrum values?
Courage, focus, openness, respect and commitment. They're part of the Scrum Guide by Ken Schwaber and Jeff Sutherland.
When should you run a Scrum Values retrospective?
Run it when a Scrum team is starting out, hitting performance problems, doing a quarterly health check, or heading into a stretch that will test how well it lives its values.
What questions does a Scrum Values retrospective ask?
Five prompts, one per value: how do we tackle tough problems (Courage), how can we improve focus on our goals (Focus), how do we stay open to new things (Openness), how do we respect each other (Respect), and how can we make our commitments a reality (Commitment).
Why do the Scrum values matter?
The Scrum Guide says that when a team lives these values, the pillars of transparency, inspection and adaptation come to life and build trust. Without them, the events tend to become rituals.
How often should you run a Scrum Values retrospective?
Once a quarter is common. Use your regular sprint retro in between, and come back to the values when something feels off.
Ready to run this retrospective?Try this retrospective live