[probotect0r]

In my experience, most retro meetings I have been in start with the scrum master asking things like "what did we do well this sprint?", followed by complete silence from the team until someone points out a non-point like "we collaborated well...".

One team I worked on decided to not pre-schedule retro meetings. Instead we had a 'retro board', which was just a section of a white board where team members would write down specific things that they think would be worth discussing in a future retro meeting. The team would decide to hold a retro meeting once the board had accumulated a few things to talk about. We found this approach was super effective because we knew what we needed to discuss when we held the meeting, instead of waiting for team members to recall something to talk about.

[maximus-decimus]

We started playing Counter Strike every retro because all we were doing was bitching against things we have no power over.

[IshKebab]

That's been my experience of regular retrospectives too. There's rarely anything notable to discuss in a 2 week period (or even a month) so it just makes for useless awkward meetings.

I like your idea.