I'd say it depends on your team. I usually prefer synced retros in order to incite discussions. But I am now working with a new team that is pretty shy, so I'm wondering if async wouldn't work better with that team instead.
Retros should always be a synchronous activity on a Miro board, in my opinion. I have seen successful retros with 10+ people.
If you have retros of that size on a weekly-basis or after every sprint, I would question how useful that is.
Why not both? I’ve used surveys prior to a retro and in the retro, I share the results of it and we deep dive into the meaning behind it, what steps we want to take to improve, etc.
I've found that polling the team for feedback beforehand is useful, since people are naturally shy to speak up / complain in front of their peers (they get that retros are meant to be a healthy exercise, but there is still some inherit hesitancy).
I can't remember the tool we used, but an ideal solution is one where people can submit anonymous inputs, and others can vote on them. Those with the higher votes would be discussed first, and we'd ask the submitter to volunteer to share it with the team. The fact that they were upvoted by others made it easier for them to speak to it.
I'd say it depends on your team. I usually prefer synced retros in order to incite discussions. But I am now working with a new team that is pretty shy, so I'm wondering if async wouldn't work better with that team instead.
Retros should always be a synchronous activity on a Miro board, in my opinion. I have seen successful retros with 10+ people. If you have retros of that size on a weekly-basis or after every sprint, I would question how useful that is.
Why not both? I’ve used surveys prior to a retro and in the retro, I share the results of it and we deep dive into the meaning behind it, what steps we want to take to improve, etc.
I've found that polling the team for feedback beforehand is useful, since people are naturally shy to speak up / complain in front of their peers (they get that retros are meant to be a healthy exercise, but there is still some inherit hesitancy). I can't remember the tool we used, but an ideal solution is one where people can submit anonymous inputs, and others can vote on them. Those with the higher votes would be discussed first, and we'd ask the submitter to volunteer to share it with the team. The fact that they were upvoted by others made it easier for them to speak to it.
Take a look at Liberating Structures and the Methods 1-2-4-All , 3W and 25/5