MENU
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?
Suggested Answer: C
Get Premium PMI-ACP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
JA
Jaleesa
11 months ago
Wait, are we really suggesting typing feedback instead of talking? Sounds odd.
PA
Paris
11 months ago
I totally agree, clustering and dot voting can really change the dynamic!
FL
Fletcher
12 months ago
Specific questions could help, but it might still leave some quiet.
SH
Sharen
12 months ago
Not sure if emailing feedback is the best idea, feels too impersonal.
BE
Belen
1 year ago
I think using silent writing is a great way to get everyone involved!
HA
Hayley
1 year ago
I’m a bit hesitant about option D. Emailing feedback seems like it could lead to less engagement during the actual meeting. I think we need more interaction.
DA
Daniela
1 year ago
I practiced a similar question where we talked about balancing participation. I think encouraging everyone to write down their feedback first, like in option C, could really help.
EA
Earlean
1 year ago
I'm not entirely sure, but I feel like asking specific questions could help get quieter team members to speak up. So maybe option B?
SH
Shenika
1 year ago
I remember we discussed how important it is to ensure everyone feels comfortable sharing their thoughts during retrospectives. I think option C might be the best approach.
GE
Gerardo
1 year ago
I feel pretty confident about this one. Option C seems like the best approach to me - using retrospective techniques to gather feedback before the discussion.
RY
Ryann
1 year ago
I'm a bit confused on this one. I'm not sure if I should go with A, B, or C. Maybe I'll review the material again before deciding.
MA
Marjory
1 year ago
Hmm, I'm leaning towards option C. Structuring the retrospective to get feedback before the discussion seems like a good way to balance things out.
SA
Sanjuana
1 year ago
I think the key is to make sure everyone's voice is heard. Using techniques like silent writing and dot voting could help with that.
SH
Shayne
1 year ago
This is a tricky one. I'm not sure if I should encourage more participation or try to structure the retrospective in a different way.
JA
Jaime
1 year ago
Okay, I've got this. The order is Vault, CPM, PSM, PVWA. I'm confident that's the right sequence.
AL
Alana
1 year ago
This one seems pretty straightforward. I'm pretty confident the image UDO would be used in the Designer pane of Page Composer.
LE
Lenita
1 year ago
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!
KA
Kati
1 year ago
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!
EL
Eleonore
1 year ago
D) Ask team members to email feedback that can be summarized in a spreadsheet for the team.
RO
Roselle
1 year ago
C) Use retrospective techniques, such as silent writing, clustering, and dot voting to field feedback prior to discussion by the team.
SA
Sanjuana
1 year ago
B) Ask more specific questions during the retrospectives.
KR
Kristel
1 year ago
A) Encourage all team members to participate, and have them type their retrospective feedback into the agile lifecycle management tool.
EL
Elly
1 year ago
Ooh, I like the idea of silent writing! That's a great way to get people thinking and sharing without the extroverts dominating.
FE
Felicia
1 year ago
B) Ask more specific questions during the retrospectives.
RO
Roxanne
1 year ago
C) Use retrospective techniques, such as silent writing, clustering, and dot voting to field feedback prior to discussion by the team.
RA
Rachael
1 year ago
A) Encourage all team members to participate, and have them type their retrospective feedback into the agile lifecycle management tool.
OC
Octavio
2 years ago
I agree that C is the correct answer. It's important to get equal participation from all team members, and those techniques help facilitate that.
SH
Shasta
1 year ago
B) Ask more specific questions during the retrospectives.
KI
Kindra
1 year ago
C) Use retrospective techniques, such as silent writing, clustering, and dot voting to field feedback prior to discussion by the team.
CA
Carman
1 year ago
A) Encourage all team members to participate, and have them type their retrospective feedback into the agile lifecycle management tool.
LA
Lashunda
2 years ago
Using retrospective techniques like silent writing could also help balance the conversation.
GE
Gerald
2 years ago
I agree with Trinidad. It's important for everyone to have a voice during retrospectives.
TR
Trinidad
2 years ago
I think the scrum master should encourage all team members to participate.
LA
Lai
2 years ago
Using retrospective techniques like silent writing could also help balance out the conversation.
CO
Cory
2 years ago
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.
AN
Annalee
2 years ago
Yes, using techniques like silent writing and dot voting can really help bring out different perspectives.
LI
Ligia
2 years ago
I agree, option C would definitely help balance out the conversation.
LO
Loise
2 years ago
I agree with Floyd. It's important for everyone to have a voice during retrospectives.
FL
Floyd
2 years ago
I think the scrum master should encourage all team members to participate.