Cross-Team Review: Break the "Happy Path"

A use case that contains only the happy path is usually incomplete. Your task is to cross-review another team's use case and challenge it with realistic "What if...?" situations to discover missing behavior and hidden assumptions.

Your Task

1. Present: One team reads an existing use case (actor, goal, basic flow) aloud.
2. Challenge: The reviewing teams listen and generate at least three distinct "What if...?" questions (e.g., regarding missing actors, timing, or abrupt exits).
3. Document: Choose the most important findings and update the original use case document. Add them as new alternate flows, exception flows, or clarification questions.

The goal is not to invent random disasters, but to find realistic edge cases. Unknown items are useful discoveries. If a domain rule is unknown to you, do not silently invent the policy for the other team; record it as a clarification question.

Exception Flow Discovery

What if the player closes the application during a storytelling scene? * Stakeholder impact: Severe player frustration from losing progress if the game starts from the very beginning. * Action: Add an exception flow (the system should auto-save at the start of each scene and resume from the saved state).

Clarification Question

What if the player does not open the virtual pet game for a whole week? * Stakeholder impact: Casual players might uninstall the game if their pet permanently dies while they are busy, whereas hardcore players might expect realistic consequences. * Action: Record an explicit clarification question to ask the stakeholder if the pet can die of starvation while the app is closed, or if its stats simply drop to a safe minimum level.