Introduction: What You’ll Learn
In this simulation, you'll guide your team through estimating a feature that isn't well-defined. You'll practice clarifying requirements, assessing complexity, and reaching a consensus on estimates.
You’ll practice:
- Extracting specific details from vague descriptions
- Structuring the breakdown of features into manageable parts
- Collaborating with the team to handle uncertainties
- Documenting assumptions and potential risks
Step-by-Step Simulation
Scene 1: Introducing the Feature
Facilitator: "Hey team! Today, we're looking at a new feature called 'Enhanced User Notifications.' The details are a bit sketchy, so let's work together to clarify what’s needed and come up with an estimate."
Facilitator: "The goal is to make our notification system more user-friendly and customizable. We don’t have all the details yet, so let’s brainstorm what this might involve."
Facilitator: "What comes to mind when you hear 'Enhanced User Notifications'? Let's jot down some ideas."
Scene 2: Gathering Input
Alex: "I think users might want to choose which notifications they get and how they get them, like via email or SMS."
Sara: "Yeah, maybe we should add different channels like push notifications or even in-app alerts."
Facilitator: "Great ideas. Do we have any user feedback that could guide us? Maybe something about how current notifications are used?"
Priya: "I remember some feedback about wanting more control over how often notifications are sent."
Facilitator: "Perfect. So it sounds like key areas are user preferences, channel options, and frequency controls. Anything else?"
Leo: "How about different formats, like detailed vs. summary notifications?"
Facilitator: "Alright, so we have preferences, channels, frequency, and formats. Let’s figure out what’s feasible for the next sprint."
Scene 3: Breaking Down the Feature
Facilitator: "To estimate, let’s break it down. Which part should we tackle first?"
Sara: "Preferences seem like a good starting point."
Facilitator: "Agreed. For user preferences, what do we need to do technically, and how would we estimate that?"
Alex: "I’d say 5 story points for changes to the database and the UI."
Facilitator: "Does everyone agree on 5 points for preferences? Next, let’s talk about channels."
Priya: "Channels might be more complex. We’ll need new integrations. Maybe 8 points?"
Leo: "Sounds right. Let’s start with a limited set of channels first."
Facilitator: "Good call. We’ll note that as an assumption. Now, let’s decide on frequency controls and formats."
Scene 4: Reaching Consensus
Facilitator: "So far, we have preferences at 5 points and channels at 8 points. For frequency controls, how about 3 points, since it's mostly settings?"
Alex: "3 sounds good. Formats could also be 3, starting simple."
Facilitator: "Great. So here’s the summary: Preferences at 5, Channels at 8, Frequency at 3, Formats at 3. Does everyone agree?"
(Team nods in agreement.)
Facilitator: "Awesome. We’ll document these estimates and our assumptions. Thanks, everyone, for your input. Let’s stay flexible in case any new requirements come up."
Mini Roleplay Challenges
Challenge 1: Someone has a very different estimate. What do you do?
- Best Response: “Let’s dig into why there’s a difference. Is it about complexity, unknowns, or something else?”
Challenge 2: A team member questions why this feature is a priority.
- Best Response: “Good question. Let's revisit the business value and make sure it aligns with our current goals.”
Challenge 3: A part of the feature remains vague despite efforts to clarify.
- Best Response: “Let’s list this as an open question and follow up with the Product team for more details.”
Optional Curveball Mode
- New requirements pop up mid-discussion.
- A team member feels ignored.
- The team argues over the estimation method.
Practice handling each situation to keep the discussion focused and productive.
Reflection Checklist
Estimation Process
- Did I facilitate a clear breakdown of vague requirements?
- Was the team engaged and working together?
Clarity and Consensus
- Did we reach consensus on estimates?
- Were assumptions and potential risks documented?
Communication Skills
- Did I probe for details without causing frustration?
- Did I guide the discussion toward actionable insights?
Common Mistakes to Avoid
- Jumping into estimates without clarifying scope
- Ignoring different opinions or lower-confidence estimates
- Not documenting assumptions and open questions