Roleplay Scenario
Scenario Overview
During a daily standup, the conversation starts to drift away from updates and priorities, turning into a vent session about recent challenges and frustrations. It’s important to acknowledge the team’s feelings while keeping the standup efficient and goal-oriented.
You need to tactfully steer the conversation back to its intended purpose without sidelining the team’s concerns but ensuring they are addressed in a more appropriate setting.
Roles & Setup
Role A – Scrum Master (You)
You're facilitating the standup and notice the conversation veering off course.
Your goal: Gently guide the team back to a productive discussion while validating their frustrations.
Role B – Developer
You’re sharing frustrations about recent blockers and challenges.
Your goal: Express concerns constructively and be open to redirection.
Role C – QA Engineer (Optional)
You’re also experiencing challenges and contributing to the venting.
Your goal: Share your perspective but remain open to refocusing the discussion.
Suggested Openers
Scrum Master:
- “I hear a lot of important concerns, and they matter. Let's cover today’s goals first, and then we can tackle these issues afterward.”
- “Thanks for sharing those points. Let’s quickly align on today’s priorities, and I’ll set up some time to dive deeper into these challenges.”
Developer:
- “I’ve been struggling with [Blocker], and it’s been frustrating. Any advice on moving forward?”
- “It’s been tough dealing with [Issue]. I’m hoping for some direction or solutions.”
QA Engineer:
- “Testing has been challenging with these changes. It’s really slowing us down.”
- “We seem to be hitting the same problems repeatedly, and it’s getting exhausting. Updates would be appreciated.”
Sample Roleplay in Action
Scrum Master:
“Hey team, I’m sensing some frustration, especially around [Blocker]. It’s crucial we address it, but let's make sure we keep today’s standup focused. How about we quickly discuss today’s key tasks and blockers, and then I’ll set up a time to really dive into these issues?”
Developer:
“Sure, it’s been overwhelming with all the blockers. For today, I’m working on [Specific Task], but I need support with [Blocker].”
QA Engineer:
“Yeah, I’m swamped with the testing backlog, but today I’ll focus on [Priority Test]. I need some clarity on when to expect fixes.”
Scrum Master:
“Great, thanks for sticking to the agenda. I’ll schedule a follow-up meeting to discuss these challenges in more detail. Let’s make sure everyone’s updates are heard today.”
Developer:
“Sounds good. I’ll save additional feedback for the follow-up.”
QA Engineer:
“Agreed, thanks for setting that up.”
Scrum Master:
“Perfect! Let’s finish with any other quick updates or blockers, then we’ll tackle these frustrations with a fresh focus later.”
Post-Scenario Tools
Curveball Mode (Optional)
Throw in one of these during the roleplay to test adaptability:
- A team member insists on continuing the venting despite attempts to redirect.
- A sudden priority change is announced mid-standup.
- Someone brings up a critical issue unrelated to the current discussion.
Reflection Checklist
As the Scrum Master:
- Did you acknowledge team concerns without dismissing them?
- Did you effectively redirect the standup back to its focus?
- Did you schedule or suggest a follow-up to address deeper issues?
As a Participant:
- Did you express concerns constructively?
- Did you remain open to refocusing efforts?
- Did you contribute to a positive, forward-looking atmosphere?
Common Mistakes to Avoid
- Ignoring frustrations without offering a plan to address them later.
- Allowing the session to be dominated by complaints.
- Failing to ensure all team members have time to share key updates.
Pro Tip
Redirecting a vent session is about balance—validate concerns, refocus swiftly, and ensure there’s a plan for follow-up. This maintains the integrity of the standup while respecting team dynamics.