Retrospectives are normally the inspect part of the agile inspect and adapt. If you are aware of or are using scrum or some other agile methodology, then running retrospectives should be nothing new. If you have never run a retrospective before, then you would have some fun things to learn.
The remit of a retrospective is to look back over a specific period of time, project, release, or simply a business change and highlight what worked well, what didn't work well, and what improvements are needed. This process can traditionally be a bit dry, so retrospectives tend to be based on games (some people refer to these as exercises, but I prefer the word "games"), which encourages collaboration, engagement, and injects a bit of fun.
As with any game, there are always rules to follow. Here are some example rules:
- Each session should be strictly time...
