YDS: How Should a Scrum Master Facilitate Their First Retrospective?

Summary

In this video transcript, Ryan Ripley and Todd Miller, professional scrum trainers at scrum.org, discuss how to facilitate a first scrum retrospective. They advise keeping it simple, focusing on inspecting the process, and adapting one or two areas. They suggest starting with scrum values and engaging all team members. The trainers also mention a past video on handling quiet team members and encourage viewers to share their experiences and tips in the comments.

Takeaways

• 🏈 **Monday Night Football Excitement**: The conversation starts with enthusiasm for the Philadelphia Eagles vs. Dallas game, setting a friendly and casual tone.
• 📅 **Daily Scrum Consistency**: Ryan and Todd have been conducting daily scrums since January 4th, 2021, emphasizing the importance of routine and consistency.
• 🎤 **Scrum.org Trainers**: Both Ryan Ripley and Todd Miller are professional Scrum trainers at scrum.org, establishing their credibility on the subject.
• 🤔 **First Retrospective Facilitation**: A Scrum Master asks for advice on facilitating their first retrospective, highlighting a common challenge for new Scrum Masters.
• 📝 **Simplification in Facilitation**: The advice given is to not overthink or overdo the retrospective, emphasizing the art of simplifying conversations.
• 🔍 **Inspecting the Process**: The core focus of a retrospective is to inspect the process, such as the definition of done, collaboration, tools, and other process aspects.
• 🚀 **One or Two Adaptations**: Aim for one or two actionable adaptations from the retrospective, keeping the outcomes focused and manageable.
• 👥 **Balancing Team Dynamics**: Be mindful of team dynamics, especially when transitioning from a developer role to a Scrum Master role.
• 🗣️ **Engaging Quiet Voices**: Ensure all team members are included in the retrospective by actively seeking their input to balance dominant and quiet voices.
• 🌟 **Scrum Values Retro**: Suggest starting the retrospective with a focus on Scrum values (Focus, Openness, Commitment, Courage, Respect) to align with Scrum principles.
• 📚 **Learning from Others**: Encourage sharing of experiences and tips in the comments for running a retro as a Scrum Master, fostering a community of learning.

Q & A

What is the significance of Monday in the conversation?

Monday is significant because it's the day of the Philadelphia Eagles vs. Dallas Monday night football game, which the speakers are excited about.

What is a daily scrum and who hosts it?

A daily scrum is a short, daily meeting in Scrum where the team discusses their progress and plans for the day. It is hosted by Ryan Ripley and Todd Miller, who are professional Scrum trainers at scrum.org.

How long have Ryan and Todd been conducting daily scrums?

Ryan and Todd have been conducting daily scrums every day since January 4th, 2021.

What is the primary purpose of the daily scrum meetings?

The primary purpose of the daily scrum meetings is to answer questions, drop knowledge, and help improve Scrum practices.

What advice does Todd give for facilitating a first retrospective?

Todd advises not to overthink or overdo it, suggesting that the art of facilitation is simplifying conversations.

What does Todd suggest as a starting point for a first retrospective?

Todd suggests starting with Scrum values such as focus, openness, commitment, courage, and respect, and discussing how they were amplified or suppressed during the sprint.

What is a common challenge Todd anticipates for a new Scrum Master facilitating a retrospective?

A common challenge is managing the dynamic of being a former peer and now the facilitator, ensuring respect for the new role and addressing any difficulties that may arise.

Why is it important to pull quiet team members into the conversation during a retrospective?

It is important to ensure that all team members contribute to the retrospective to gain diverse perspectives and prevent the discussion from being dominated by a few strong voices.

What is the recommendation for the number of adaptations to the process after a retrospective?

The recommendation is to aim for one or two adaptations to the process, focusing on simplicity and practicality.

What is the role of the team in a Scrum Master's first retrospective?

The team plays a crucial role as they are the ones who want the Scrum Master to be successful and should be supportive of the process.

How can one find past discussions on handling quiet team members?

Past discussions can be found in the video archives, specifically episode 50 something out of almost 200.