Introduction: What You’ll Learn
This simulation helps you handle a common planning hiccup — discovering a missed dependency partway through the sprint. You'll learn to adjust the sprint plan, keep everyone in the loop, and ensure the team stays on track with minimal disruption.
You’ll practice:
- Spotting and addressing missed dependencies
- Tweaking the sprint plan on the fly
- Communicating changes clearly to your team and stakeholders
- Keeping the team focused and moving forward
Step-by-Step Simulation
Scene 1: Getting Started with Sprint Planning
Facilitator: "Hey everyone, welcome to sprint planning. This time, we’re focusing on beefing up user authentication and boosting app performance. Let’s dive into the backlog and pick our top priorities."
(The team discusses, estimates, and assigns tasks for the sprint.)
Facilitator: "Awesome, we’ve got our sprint set. Keep an eye out for any dependencies as you go."
Scene 2: Discovering the Missed Dependency
(Mid-sprint, Alex brings up an issue during a daily check-in.)
Alex: "Hey team, I just realized we need an updated encryption library for the auth updates, and it’s not in our sprint backlog."
Facilitator: "Good catch, Alex. Let’s figure out how to handle this before it throws us off track."
Scene 3: Dealing with the Dependency
Facilitator: "First off, let’s see how much this dependency affects our sprint goals. Can we finish the auth enhancements without it, or is it a must-have?"
Sara: "It’s a must-have for the security updates. Without it, we’re stuck."
Facilitator: "Okay, let’s see what we can shuffle around. Maybe we can push a lower-priority task to the next sprint?"
Priya: "How about the performance tweaks? They’re not as urgent."
Facilitator: "Sounds good. Let’s move the performance stuff to the backlog and bring in the encryption task. I’ll update the sprint board and let stakeholders know."
Scene 4: Keeping Everyone in the Loop
Facilitator: "Quick update: We found a critical dependency for our auth updates. We’ve adjusted our sprint to include the encryption library and postponed some performance tasks."
Leo: "Should we loop in the product team?"
Facilitator: "Definitely. I’ll shoot them a message after this meeting to keep everyone on the same page."
Mini Roleplay Challenges
Challenge 1: A team member is worried about delaying performance tasks.
- Best Response: “Let’s consider the impact — we need the dependency to ensure our core functionality is solid.”
Challenge 2: The product team questions the change in priorities.
- Best Response: “This adjustment keeps our auth updates secure. We can chat about any concerns for the next sprint.”
Challenge 3: A team member is confused about how the dependency affects their work.
- Best Response: “Let’s break down what the encryption library means for your tasks. I’ll walk you through it.”
Optional Curveball Mode
- Another dependency surfaces later in the sprint.
- A critical task turns out to be bigger than expected.
- Stakeholders ask for more features mid-sprint.
Practice staying focused on sprint goals despite these challenges.
Reflection Checklist
Response and Adjustment
- Did I spot and deal with the dependency quickly?
- Was the sprint plan adjusted smoothly?
Communication
- Did I clearly explain changes to the team and stakeholders?
- Did I make sure everyone understood why we made the changes?
Leadership and Adaptability
- Did I guide the team through the change without a hitch?
- Was I ready to handle any additional surprises?
Common Mistakes to Avoid
- Ignoring or downplaying the dependency
- Not communicating changes thoroughly
- Overloading the team without reprioritizing tasks
- Failing to update the sprint board and related docs