#user-stories

Facilitate a user story mapping session for product planning. Process: 1. Define user personas and their goals. 2. Map user activities (horizontal backbone). 3. Break down activities into tasks (vertical stories). 4. Prioritize stories into releases (MVP, V2, V3). 5. Identify dependencies and risks. 6. Estimate effort and value. Use collaborative tools (Miro, Mural). Output: visual story map with clear release plan. Include acceptance criteria for each story. Align team on product vision and roadmap.

Write clear user stories with testable acceptance criteria. Format: 'As a [persona], I want [functionality], so that [benefit].' Example: 'As a returning customer, I want to save my payment information, so that I can checkout faster on future purchases.' Acceptance criteria using Given-When-Then: Given I'm a logged-in user, When I reach checkout with previously saved payment methods, Then I should see my saved cards as options, And I can select one with a single click, And the form auto-fills payment details. Include edge cases: expired cards, declined payments, first-time users. Definition of Ready: story has clear acceptance criteria, designs attached, effort estimated, dependencies identified. Definition of Done: feature tested, documented, deployed, analytics tracking added.