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 is a focused session that helps teams evaluate and strengthen their alignment with the five fundamental values that form the foundation of Scrum: Courage, Focus, Openness, Respect, and Commitment. This retrospective format encourages team members to reflect on how well they embody these values in their daily work and identify opportunities for improvement. By examining each value separately, teams can have meaningful discussions about their behaviors, challenges, and successes in living up to these principles. Originally outlined in the Scrum Guide by Ken Schwaber and Jeff Sutherland, these values are essential for building trust, fostering collaboration, and creating a healthy team culture. This retrospective helps teams move beyond mechanical process adoption to embrace the true spirit of Scrum.

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 refers to the team's ability to concentrate on current sprint work and project goals. Guide the discussion toward identifying distractions and ways to maintain better focus. Consider both individual and team-level focus challenges.

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 the team is new to Scrum and needs to understand the values better
  • During times when team dynamics or performance issues suggest a disconnect from core values
  • As part of quarterly team health checks to ensure alignment with Scrum principles
  • When preparing for significant changes or challenges that will test the team's foundation

Suggested icebreaker questions

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

Ideas and tips for your retrospective meeting

  • Encourage specific examples rather than general statements to make the discussion more actionable
  • Use the Values Radar technique to visualize the team's current state for each value
  • Create a safe space for honest discussion by acknowledging that living these values is a journey
  • Consider discussing one value per day leading up to the retrospective to allow deeper reflection
  • Document concrete actions for improvement for each value to track progress
  • Use real scenarios from recent sprints to illustrate how values are being lived (or not)

New to retrospectives? Read our guide on how to run a retrospective →