There is a big continuous improvement drive at work and the simplest tool for continuous improvement is the retrospective. It’s the reason we do one every sprint. So we can find out what is stopping us from doing things better. It’s so we improving things in our environments bit by bit. As a SCRUM master, I find Retrospectives as one of the most important tools to master.
But haven’t you found that after a few they end up being nothing more than a complaint session, or they simply don’t return anything to the team. No return on investment soon breeds apathy. The team just sit in the meeting because they have to do it because the SCRUM master said so. This is the time to do something counter-intuitive. Have a retrospective on the retrospective. Keep it short and try and get an action from it. Soon you’ll see why. It’s something you are doing in the retrospective making them ineffective or the same action appear unresolved over and over. And for the long-term improvement of the team, you’ll have to resolve them.
Try to do one today.
Christchurch Scrum 
Retrospectives are interesting in a team environment but when using scrum in a solo pursuit, how do you think you can keep motivated to do a retrospective regularly? I mean, you know which work needs doing, so you do it. Yes, somethings are never resolved no matter how long you keep trying to push it through. How can I get to those things that never get into the in progress column?
Another perspective on Retrospectives:
http://www.estherderby.com/2011/06/promoting-double-loop-learning-in-retrospectives.html