Performing regular retrospectives

One time, while teaching and coaching on Scrum implementation, a programmer asks me, How often should we do the daily Scrum? Well, the obvious answer is: daily. With retrospectives, the answer is not that obvious, so let's see how often, in which moment, using which methods to retrospect.

And don't forget the reason for retrospection: complaining and whining, without solving anything – no! The reason for spending time with retrospectives is continuously changing smaller or bigger aspects so that you can continuously improve.

How often we should retrospect

You need to retrospect more often when you start pair programming in the team. My typical recommendation for starters is to have a retrospective every week. After you stabilize your work, chat with the team and let them decide.

You can have planned retrospectives (for instance, every Tuesday at 14:00 or even every Tuesday at 12:00), but you can also have retrospectives...