A project retrospective is completed at the end of a project. The frequency is also different - single team retrospectives are typically run at the end of Sprint or delivery of a work product. Luke: The number of people involved means that you cannot cost-effectively conduct traditional retrospectives. InfoQ: In your opinion what is it that makes huge retrospectives different from team or project level retrospectives? Put another way, "huge" means "too much money to get them into the same room"! Scalable enterprise retrospectives provide a solution to improve enterprise performance when many teams are involved. Luke: By huge, I mean hundreds of attendees, quite likely organized in multiple locations and time zones. InfoQ: Your article talks about doing huge retrospectives with many attendants.
![sailboat retrospective luke hohman sailboat retrospective luke hohman](https://blog.myagilepartner.fr/wp-content/uploads/2023/08/sailboat-retrospective.jpg)
InfoQ interviewed Luke about organizing huge retrospectives, analyzing the data, and following up on the actions from such retrospectives. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann wrote the blog post how to run huge retrospectives across dozens of teams in multiple time zones in which he describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved. Agile retrospectives are mostly done at the team level or at a project level.