Roleplay Scenario
Scenario Overview
You're leading a daily standup for your engineering team. The project is moving forward, but a few mild blockers have cropped up, like dependencies and task clarifications. Your goal is to ensure everyone is on the same page, address these blockers efficiently, and keep the team motivated.
Roles & Setup
Role A – Standup Leader (You)
You're the facilitator of the standup.
Your goal: Keep the meeting focused, address blockers, and maintain team motivation.
Role B – Developer 1
You're working on a critical feature but facing a dependency issue with another team.
Your goal: Communicate your progress and seek help to resolve the blocker.
Role C – Developer 2
You're progressing well but need clarification on a specific task from the product owner.
Your goal: Share your updates and seek guidance where needed.
Role D – Scrum Master (Optional)
You're here to support the team in resolving impediments.
Your goal: Provide additional resources or guidance if necessary to help resolve blockers.
Suggested Openers
Standup Leader:
- “Morning, team! Let’s do a quick round of updates. Keep it to what you did yesterday, what you’re tackling today, and any blockers.”
- “Thanks for joining. Let's get aligned and tackle any blockers head-on.”
Developer 1:
- “I’m working on [Feature X]. Progress is good, but I'm stuck waiting for data from the API team.”
- “Moving along with my tasks, but I need some API data to proceed.”
Developer 2:
- “I’ve finished most of the UI components. I need some clarification on the specs for validation from [Product Owner].”
- “Things are going well, but I need guidance on a validation requirement.”
Scrum Master:
- “I’m here to help with any blockers. Let’s ensure everyone’s clear on what to do next.”
Sample Roleplay in Action
Standup Leader:
“Morning, team! Let’s kick things off with [Developer 1]. Any updates or blockers?”
Developer 1:
“Sure! I made progress on [Feature X], but I’m blocked waiting on data from the API team. I could use some help getting that moving.”
Standup Leader:
“Thanks for flagging that. I’ll touch base with the API team after this meeting to get an update. [Developer 2], how are things on your end?”
Developer 2:
“I’m wrapping up the UI components and need some clarification on the validation specs. I’ll catch up with [Product Owner] later today.”
Standup Leader:
“Sounds good. Let’s make sure you get the clarification you need. [Scrum Master], any ideas on how we can speed up resolving these issues?”
Scrum Master:
“I’ll contact the API team right after this and see if we can prioritize that dependency. For the validation, maybe a quick chat with [Product Owner] will help clarify.”
Standup Leader:
“Great! Let’s regroup tomorrow and keep everyone posted on progress. Thanks, team!”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce one of these mid-roleplay to test adaptability:
- A new blocker arises that affects multiple team members
- A team member is disengaged and not participating
- An urgent task needs to be prioritized suddenly
Reflection Checklist
As the Standup Leader:
- Did you keep the meeting on track and focused?
- Did everyone have a chance to speak and was heard?
- Did you facilitate solutions to blockers without taking over?
As a Participant:
- Did you communicate your updates and blockers clearly?
- Did you seek help effectively if needed?
- Did you contribute constructively to solving any issues?
Common Mistakes to Avoid
- Letting the standup run too long or get off-topic
- Not addressing blockers effectively
- Overlooking quieter team members who may need help
- Ending without clear next steps or resolutions
Pro Tip
A well-run standup fosters team cohesion and productivity. Encourage openness, stay solution-focused, and keep the momentum going throughout the sprint.