At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
This is often one of the first things to be dropped from a team’s implementation of Agile methodologies: the Retrospective. It is a shame, too, because the team that does this will, over time, operate more smoothly and with ever increasing velocity and job satisfaction.
The retrospective is more than just a ‘bitch session.’ Recognizing what went well is a key element in getting people to open up and participate.
The ‘negatives’ should also be constructive. Divide them up into categories: What is within the team’s power to control? What is outside of their control but can be influenced by them? What items are they completely powerless to change? Then for those where there is control or influence, identify the change that will help make the problem better. Resolve as a team to implement those changes.
But there is more. This time can be used to do anything that will make the team more effective. Learn new technologies. Meet with the business users. Get some Agile training!
Bottom line: Do it. Don’t skip it.