Being comfortable with the team is a big part of course, but this doesn't help you as the team lead since getting people to 'be comfortable' is not a single ste

Being comfortable with the team is a big part of course, but this doesn't help you as the team lead since getting people to 'be comfortable' is not a single step task. I recommend trying some of the following: - Create a list of topics for your team to complain about at the retro. eg. Bugs, communication, management, programming practices, meetings... This should help stir some memories and emotions. - Insist that each person give at least one piece of feedback. If someone is not willing to give feedback, make a silly suggestion for them. For example, in our last retro, a member was on holidays for 2/3rds of the sprint, and said he didn't have any 'good' feedback to give. I jokingly suggested that he was glad his holidays were over and he was able to be back at work with his team. A bit of humour helps break the ice. Any feedback, no matter how silly, is better than none at all. - Take notes of any negative feedback during the sprint. If the retro lacks engagement, bring up one of these topics as a discussion point. People are forgetful - they may need some prompting! - Take note of things you see need improving (use that 80/20 analysis). Bring these up as discussion points at the retro. Remember, you are there to facilitate the team. But that doesn't mean you don't get involved. Lead the discussion when it runs dry, and don't be afraid to make suggestions. Show that you are passionate about improving the team and this will leak into the team 'culture' (that dreaded term!).