During sprint retrospectives, some team members are very vocal and tend to dominate the conversation, while others are more reserved and less likely to participate. What should the scrum master do?
Hold up, are we sure the scrum master isn't just going to use that spreadsheet to play a rousing game of Tetris during the retrospective? Talk about a team-building exercise!
Yeah, C is definitely the way to go. Although I do like the idea of emailing feedback in a spreadsheet. That could be a fun way to get people excited about data visualization!
I think option C is the best approach. Using retrospective techniques like silent writing and dot voting allows everyone to have a voice and ensures that the quieter team members aren't drowned out.
Lenita
5 days agoKati
7 days agoElly
8 days agoOctavio
26 days agoShasta
10 days agoKindra
11 days agoCarman
12 days agoLashunda
1 months agoGerald
1 months agoTrinidad
1 months agoLai
1 months agoCory
1 months agoAnnalee
19 days agoLigia
20 days agoLoise
1 months agoFloyd
1 months ago