During the last stop, you learned about sprint reviews. Now, your sprint is coming to a close and it's time to learn about retrospectives.

Download your copy of the 'Look Back in Agile: The Sprint Retrospective' eBook and learn more about retrospectives, including who to invite to the retrospective, how to conduct a retrospective meeting, how games can help make the retrospective both productive and fun, and what to do with the information gathered in the meeting.

Excerpt: In the words of a popular GPS navigation system, "You have reached your destination." You're at the end of the trail, standing on the big X on the map. The sprint is finally complete, the product has been demonstrated in the sprint review, and everyone can relax, right?

Not exactly.

Even though the sprint review takes place on the last day of each sprint, the sprint is not closed until the team has held their retrospective. (While we could call it the "lessons learned" or "post mortem," the term most often associated with Agile in general, and Scrum in particular, is "retrospective.") The sprint retrospective is usually held after the sprint review, allowing the team to reflect on the entire sprint, including the review. However, sometimes scheduling conflicts make it necessary to have the retrospective before the sprint review.

Continue your exploration, download the eBook.