Roleplay Scenario
Scenario Overview
You're in a planning session to estimate a new feature that has vague requirements. It's important to figure out what we know, identify what's unclear, and work together to come up with a realistic estimate. The goal is to make sure everyone’s on the same page and comfortable with the timeline.
Roles & Setup
Role A – Product Owner (You)
You have a rough idea of the feature but need more details to finalize the backlog.
Your goal: Clarify the feature, facilitate discussion, and help the team arrive at a realistic estimate.
Role B – Engineer
You need more clarity on technical details and potential challenges.
Your goal: Understand the feature, identify technical hurdles, and contribute to a feasible estimate.
Role C – Designer (Optional)
You’re handling the UI/UX side of things.
Your goal: Identify design needs and any dependencies that could affect the timeline.
Role D – QA Lead (Optional)
You’re focused on testing requirements and potential risks.
Your goal: Make sure testing time is included in the estimate and that acceptance criteria are clear.
Suggested Openers
Product Owner:
- “Let’s talk about estimating the new feature [Feature Name]. The requirements are a bit vague, so let’s figure out what we know and what we need to learn.”
- “I want us to share our initial thoughts on [Feature Name] and figure out the work involved. We can address any unclear parts together.”
Engineer:
- “I’ve looked at the initial requirements, and I think we need more detail on the API interactions. Can we clarify those?”
- “I'm curious about potential edge cases for this feature. Should we consider any specific scenarios in our estimation?”
Designer:
- “For the UI, should we use any existing design patterns, or are we creating something new? I want to make sure we’re aligned before starting.”
- “I'll need some time to prototype the user flow. Is there a specific area we should focus on?”
QA Lead:
- “I’d like to talk about the acceptance criteria and any specific test scenarios you have in mind. This will help us set a realistic timeline for testing.”
- “Are there any performance or security considerations we need to think about?”
Sample Roleplay in Action
Product Owner:
“Thanks for joining. We have this new feature, [Feature Name], that stakeholders are excited about. The requirements are a bit high-level, so let’s break down what we know and what we still need to figure out for a solid estimate.”
Engineer:
“I see that the feature will involve some new API integrations. Can we get more specifics on the data requirements and expected interactions?”
Designer:
“I’m thinking about the UI impacts and want to make sure we’re using our existing design system. Do we have particular user experiences in mind that this feature should align with?”
QA Lead:
“For QA, having clear acceptance criteria is key. Are there any specific scenarios that need testing emphasis, especially regarding performance?”
Product Owner:
“Great questions. Let’s coordinate with the backend team for API details. For design, let’s stick to our current patterns unless new requirements pop up. QA, I’ll draft some initial user stories and scenarios for us to refine.”
Engineer:
“That sounds good. Once we have more API information, I can help draft a detailed technical plan.”
Designer:
“I’ll start with wireframes using our design guidelines and share them for feedback before moving to high-fidelity designs.”
QA Lead:
“I’ll outline a preliminary test plan and make sure any performance benchmarks are clear, especially if this feature might impact system load.”
Product Owner:
“Perfect. Let’s regroup once we have more information for a precise estimation session. Thanks for the input, everyone.”
Post-Scenario Tools
Curveball Mode (Optional)
Introduce one of these challenges to see how participants adapt:
- A new requirement is introduced mid-discussion that could impact scope.
- The team realizes a critical dependency was overlooked.
- Stakeholders push for a tighter timeline without additional resources.
Reflection Checklist
As the Product Owner:
- Did you facilitate the conversation to uncover unknowns?
- Did you encourage team input and collaboration?
- Did you help guide toward a realistic estimate?
As a Participant:
- Did you communicate your concerns and needs clearly?
- Did you contribute constructively to the estimation process?
- Did you help identify risks or dependencies?
Common Mistakes to Avoid
- Overlooking key dependencies or risks
- Rushing to an estimate without sufficient detail
- Not seeking input from all relevant roles
- Letting the conversation get sidetracked by unrelated issues
Pro Tip
In situations with vague requirements, focus on collaboration and open communication. This ensures everyone is aligned and the estimate is grounded in reality, not guesswork.