How do we facilitate an effective Sprint Retrospective for a remote-first team?

All answers to this question.

Remote Retros need high "Visual Collaboration." Switch from a doc to a tool like Miro or Mural. Try the "Sailboat" format: the boat is the team, the "Wind" is what pushes you forward (strengths), and the "Anchor" is what’s holding you back (impediments). Another great one is the "Four Ls": Liked, Learned, Lacked, and Longed For. To keep it safe and honest, allow for "Anonymous Posting" of sticky notes initially. This prevents "HIPPO" (Highest Paid Person's Opinion) bias. Most importantly, ensure the Retro results in at least one "Action Item" that is added to the next Sprint Backlog with a clear owner.

   Answered 2025-01-07 by Elizabeth Martinez

How do we prevent the Retrospective from turning into a "Moan-fest" where we just complain about things we can't actually change, like company-wide policies?

   Answered 2025-01-09 by Steven Clark

• You should use the "Circle of Influence" technique, Steven. Categorize every complaint into three buckets: Things we "Control" (team level), things we "Influence" (department level), and things we just have to "Adapt To" (company level). Focus 90% of the Retro energy on the "Control" bucket. For things in the "Influence" bucket, the Scrum Master’s action item is to take that feedback to the relevant leadership. This keeps the meeting productive and prevents the team from feeling helpless, as they are actively working on changes that are within their immediate reach.

     Commented 2025-01-11 by Anthony Lewis

We started a "Kudos" section at the start of every Retro to celebrate small wins. It changed the whole energy of the meeting from negative to constructive.

   Answered 2025-01-13 by Barbara Robinson

• Spot on, Barbara. Positive reinforcement is a key part of TQM and Scrum. Mark, try the "Sailboat" format next time; it’s a visual game-changer for remote teams.

     Commented 2025-01-15 by Elizabeth Martinez