Roleplay Scenario
Scenario Overview
You're in a sprint planning meeting. As the team discusses tasks, you realize some dependencies that should have been identified earlier. These could affect the timeline and delivery of key features if not addressed.
Your task is to identify these dependencies, understand their impact, and work with the team to adjust the plan, all while keeping the conversation positive and productive.
Roles & Setup
Role A – Team Lead (You)
You're leading the planning session.
Your goal: Spot missing dependencies, figure out their impact, and guide the team in adjusting the plan.
Role B – Developer
You're responsible for implementing features and might have insights into technical needs.
Your goal: Point out any technical dependencies or risks that could affect the timeline.
Role C – QA Engineer (Optional)
You're focused on testing and ensuring quality.
Your goal: Highlight testing needs and any potential bottlenecks.
Suggested Openers
Team Lead:
- “Let’s go over our sprint tasks and spot any dependencies we might have missed.”
- “As we plan, call out any dependencies or risks we haven’t captured yet.”
Developer:
- “I just realized the new authentication feature needs a library update we haven't scheduled.”
- “Are we considering the integration work with the third-party service?”
QA Engineer:
- “I see testing dependencies that might need extra setup. We should address these to avoid delays.”
- “We’ll need some test data from the backend—is that lined up?”
Sample Roleplay in Action
Team Lead:
“Hey everyone, thanks for joining the planning session. As we plan our next sprint, let's make sure we're not missing any important dependencies that might affect our timeline.”
Developer:
“I’ve noticed that the new authentication feature needs a library update we haven’t scheduled yet. We should slot that in.”
QA Engineer:
“Good point. For testing, we’ll need some test data from the backend team for the new authentication flows. Have we planned for that?”
Team Lead:
“Great catches. Let’s update the backlog to include the library update as a prerequisite for the authentication work. We’ll also need to coordinate with the backend team to ensure the test data is ready.”
Developer:
“I can handle the library update. I’ll sync with the backend team to confirm when they can provide the test data.”
QA Engineer:
“With those updates, I’ll plan the testing schedule more accurately and avoid any bottlenecks.”
Team Lead:
“Perfect. This keeps us on track. Let’s document these dependencies and adjust our plan. I’ll also update other teams if needed.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce unexpected challenges to test adaptability:
- A dependency has a longer lead time than expected.
- An unexpected team absence affects planned tasks.
- A stakeholder introduces a new high-priority feature late in planning.
Reflection Checklist
As the Team Lead:
- Did you help the team spot all potential dependencies?
- Did you ensure everyone's insights were considered?
- Did you adjust the plan and communicate changes clearly?
As a Participant:
- Did you actively help identify dependencies?
- Did you communicate any potential risks effectively?
- Did you collaborate to find solutions and adjust priorities?
Common Mistakes to Avoid
- Overlooking cross-team dependencies
- Failing to document or communicate identified dependencies
- Not adjusting timelines or priorities when needed
Pro Tip
Encourage open dialogue during planning sessions to uncover hidden dependencies early. Being proactive can prevent disruptions and help ensure a smoother sprint.