One of the many recommended Agile practices is to conduct retrospectives at different intervals during and after a project. For those of you who are unfamiliar with the concept, in their seminal book Agile Retrospectives, Esther Derby and Diana Larsen define a retrospective as, a special meeting where the team gathers after completing an increment of work to inspect and adapt the methods and teamwork. This process of inspection and then adaptation has many salutary effects (listed by Derby and Larson), including improved productivity, improved capability, improved quality, and increased capacity. Here at Pinnacle, as part of our custom development process, we faithfully conduct retrospectives at least once every two iterations and at the end of each release because we have seen these benefits. However, in this post I want to reflect on a few of the less tangible benefits I have observed.