I have just facilitated a Scrum team String retrospective. The following activities sequence worked really well. The team had about 15 participants geographically distributed. We did use Google Drawing as the shared distributed canvas. The retrospective took 50 minutes, with great effective prioritized conversations, shared understanding for everyone’s opinions and a few action items.

Below is the agenda (with activities selected):

  1. Context: This is a Sprint (bi-weekly) retrospective for the ABC team
  2. Prime Directive:  ‘Regardless of what we discover, we understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.’ (Project Retrospectives, Kerth)
  3. Check-in: the happiness radar
  4. Main Course: Open the box
  5. Filtering: Plus, Minus Voting
  6. Check-out: Who-What-When