

Class Registration
The folks at Integrum, a rails consulting company, produced a short podcast talking about their challenges running single retrospectives with multiple teams. One of the comments from early in the podcast was when you have many teams in single retrospective, the participants tend to speak in generalities and skip the details of what happened in their team. Presumably because that information would not be of interest to the other folks not on their teams.
I have facilitated both single team and multi-team retrospectives and my experiences match the ones described by the people at Integrum. I generally prefer to run single team retrospectives, but there are times when a multi-team retrospectives. In my experience, these are two reasons why I might want to do multi-team retrospectives:
Agile Agile Design Agile SD Book Reviews Burndown Charts Certified Product Owner Certified ScrumMaster Class Design Coaching Collaboration Communication Conferences CSP Fast Pass Daily Scrum Definition of Done Design Excellence Design for Six Sigma Distributed Teams Documentation Español Estimating & Planning Extreme Programming Games Innovation Games Interviews Intro to Scrum Lean Legacy Code Links of the Week Measures Meetings Metrics Migration Movies Open Workspace Pair Programming Personal Planning PMI Powerful Questions Practices Presentations Press Release Product Backlog Product Owner Quality Refactoring Retrospectives Rugby Scrum ScrumMaster ScrumMaster Plus Servant Leadership Simple Design SIMSOC Spain Sprint Backlog Sprint Goal Sprint Planning Sprint Review Stakeholders Task Board Team Test-Driven Development Testing The Core Tools Training Training From the Back of the Room Transitions Travel Uncategorized User Stories Vision Voice of the Customer