Roleplay Scenario
Scenario Overview
Midway through a sprint, a key stakeholder requests additional features that weren't initially planned. The team is already stretched with existing commitments, and you need to address these changes without derailing the sprint goals.
Roles & Setup
Role A – Team Lead (You)
You're responsible for balancing stakeholder requests with the team’s capacity.
Your goal: Communicate effectively with stakeholders and propose adjustments without compromising core sprint objectives.
Role B – Stakeholder
You have a vested interest in additional features being included in this sprint.
Your goal: Advocate for the new features while understanding the team's constraints and priorities.
Role C – Scrum Master (Optional)
You facilitate the process and ensure the team adheres to agile principles.
Your goal: Support the team in navigating the changes smoothly and maintaining focus on the sprint goal.
Suggested Openers
Team Lead:
- “Thanks for meeting on short notice. We’ve had some new priorities come up, and I’d like to discuss how we can best accommodate them within our current sprint constraints.”
- “I’ve noticed a few new requests have surfaced, and I want to ensure we align them with our current sprint objectives.”
Stakeholder:
- “I appreciate the update. We’ve received new feedback that’s driving some of these requests. Let’s find a way to incorporate them if possible.”
- “Thanks for bringing this up. There are some important items we’d love to see included if we can manage it.”
Scrum Master:
- “Let’s keep this discussion focused on how we can adapt effectively without overloading the team.”
- “I’m here to assist in adjusting the plan while keeping our agile practices intact.”
Sample Roleplay in Action
Team Lead:
“Thanks for joining. I wanted to touch base because we’ve received some additional feature requests for this sprint. Given our current commitments, it’s crucial we discuss how best to integrate them without impacting our primary objectives.”
Stakeholder:
“I understand. These new features are based on recent user feedback and are quite crucial. How do you propose we proceed?”
Team Lead:
“I see their importance. To accommodate these without overstretching the team, we might need to reprioritize or defer certain tasks to the next sprint. Let’s identify which new requests are absolutely critical.”
Scrum Master:
“Great approach. Let’s ensure we’re clear on the priorities and keep the team’s workload balanced.”
Stakeholder:
“The user interface improvements are a top priority due to their impact. If we can focus on those, I’d be open to pushing other items to the next sprint.”
Team Lead:
“Agreed. We can adjust the current workload to prioritize the UI improvements and communicate any changes to the team. I’ll ensure the backlog reflects these updates.”
Scrum Master:
“I’ll help facilitate the changes and update the team during our next stand-up. Thanks for your flexibility.”
Stakeholder:
“Thanks for being accommodating. Keeping the team informed is key—I’ll make sure our side also aligns with any updated timelines.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce one of these unexpected elements during the roleplay:
- A new, high-priority bug is discovered that requires immediate attention.
- Stakeholder insists all requests are non-negotiable and must be included.
- Another team member expresses concerns about burnout due to added scope.
Reflection Checklist
As the Team Lead:
- Did you clearly communicate constraints and possibilities?
- Did you engage stakeholders in prioritizing effectively?
- Did you maintain a balance between accommodating requests and protecting the team?
As the Stakeholder:
- Did you communicate the urgency and importance of your requests?
- Were you open to negotiating priorities with the team?
- Did you contribute to finding a solution that supports the team's capacity?
As the Scrum Master:
- Did you support the team in maintaining agile principles?
- Did you facilitate a constructive and solution-oriented discussion?
- Did you ensure next steps were clear and actionable?
Common Mistakes to Avoid
- Agreeing to all requests without assessing impact
- Failing to communicate changes to the team clearly
- Ignoring team feedback or signs of overload
- Letting the conversation become one-sided
Pro Tip
Approach these conversations with transparency and collaboration. Emphasize shared goals and mutual understanding to navigate mid-sprint changes effectively.