Each Scrum Sprint should produce two results: 1) A product or service which is an increment of functionality closer to delivery and 2) a better, happier, more productive team. Peter Stevens explains that the retrospective is the primary opportunity for achieving the second result.
This series of articles was created to help you get the practice of retrospectives built into your company. It walks through the approach, necessary roles, in addition to guides for each role to help your company get started quickly.
Erin Beierwaltes gives some interesting tips to improve retrospectives and propose an agenda for them.
This blog post provides an inside view on how a Scrum team runs retrospectives.
Retrospectives are a powerful tool for facilitating continuous improvement. This workshop shows how to use retrospectives to put your team on a path of continuous improvement.
If you have never experienced a well-run retrospective, then it is hard to imagine what it is like by simply reading a book. Nevertheless, the article “An anatomy of a retrospective” tries to tie many of the discussions into a single experience. It is based on one real-life retrospective, but spiced up with a few pieces from other retrospectives. I’m certain the participants would recognize themselves, but I hope I have changed enough of the trivia to protect their privacy.
In his article “Effective Retrospectives & Reviews” Marco Mulder illustrates how Scrum teams can continuously improve by using a combination of their definition of done, working agreements and the product backlog.