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
1 months agoKati
1 months agoSanjuana
10 days agoKristel
17 days agoElly
1 months agoRoxanne
2 days agoRachael
10 days agoOctavio
2 months agoShasta
1 months agoKindra
1 months agoCarman
1 months agoLashunda
2 months agoGerald
2 months agoTrinidad
2 months agoLai
2 months agoCory
2 months agoAnnalee
1 months agoLigia
2 months agoLoise
2 months agoFloyd
2 months ago