One of the Principles Behind the Agile Manifesto is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” This reflection is often called a retrospective and ideally occurs on the last day of a sprint or iteration after a sprint/iteration review but before the next one is planned. As a feedback loop, retrospectives directly support the “inspect-and-adapt” aspect of Agile by giving the team the opportunity to review its own performance and identify any improvements needed. But retrospectives are not only about fixing problems. Healthy retrospectives also identify best practices that can benefit other teams, reinforce the team’s sense of ownership, and cultivate its self-organizing nature.  Read more (8 Tips for More Rewarding Retrospectives)to find out how to make your retrospectives more rewarding.