How can we facilitate an effective Sprint Retrospective for a fully remote, global Agile team?

All answers to this question.

The key to remote "Retros" is psychological safety and varied formats. Stop using the "Start, Stop, Continue" format every time. Try the "Sailboat" or "The 4 Ls" (Liked, Learned, Lacked, Longed For). We use anonymous voting tools so junior members feel safe critiquing the process without fear of judgment from leadership. Also, we rotate the facilitator role every Sprint. When a developer has to lead the session, they tend to be more engaged. We also spend the first 5 minutes on a non-work "icebreaker" to build the social capital that you normally get in an office hallway.

   Answered 2024-11-10 by Michelle Garcia

Do you find that keeping cameras on is mandatory for engagement, or does it contribute to "Zoom fatigue" during these longer sessions?

   Answered 2024-11-15 by Thomas Baker

• Thomas, we actually made cameras optional but encouraged for the "sharing" phase. To fight fatigue, we keep the session strictly to 45 minutes. If we haven't identified 2-3 "Action Items" by then, we table the rest. The goal is quality of insights, not the quantity of sticky notes on a screen.

     Commented 2024-11-18 by George Harris

We started using a "Kudos" wall before the critique phase. Starting with appreciation for teammates changes the entire tone of the meeting to be more constructive.

   Answered 2024-11-22 by Laura Nelson

• I love the Kudos wall idea, Laura. It balances the "what went wrong" with "what went right," which is essential for team morale in a remote setting.

     Commented 2024-11-25 by Ashley Young