# User Story Mapping Exercises

## Exercise 1: Build a Map from Scratch

**Task:** Create a complete story map for "Plan a weekend trip" (user: leisure traveler). Include: backbone (4–5 activities), body (2–4 tasks per activity), and a walking skeleton release line.

**Validation:**
- [ ] Activities are user actions (verbs), not features
- [ ] Tasks are specific enough to implement
- [ ] Left-to-right order reflects the natural journey
- [ ] Walking skeleton includes the minimum path to "trip planned"

**Hints:**
1. Example activities: Discover destinations → Compare options → Book → Prepare
2. "Book" might include: Choose dates, Select accommodation, Enter payment, Confirm
3. Walking skeleton = one path through; variations and extras go below the line

---

## Exercise 2: Slice Multiple Releases

**Task:** Using your "Plan a weekend trip" map (or any map you've built), define three releases: MVP, Release 2, Release 3. For each, list the new tasks and the user outcome that release enables.

**Validation:**
- [ ] Each release has a clear outcome (e.g., "MVP: Book a basic trip")
- [ ] Release 2 builds on Release 1; Release 3 builds on Release 2
- [ ] No release includes tasks that depend on later releases
- [ ] You can explain why each task landed in its release

**Hints:**
1. MVP = core happy path only
2. Release 2 might add: multiple payment options, cancellation, itinerary export
3. Release 3 might add: recommendations, social sharing, loyalty rewards

---

## Exercise 3: Convert Map to User Stories

**Task:** Take the Release 1 slice from Exercise 1. Write user stories for each task. Add acceptance criteria using "Given / When / Then" or a checklist format.

**Validation:**
- [ ] Each task maps to at least one user story
- [ ] Stories follow "As a [user], I want to [action] so that [outcome]"
- [ ] Acceptance criteria are testable
- [ ] Stories are ordered by journey sequence

**Hints:**
1. One task can become multiple stories if it's complex
2. Acceptance criteria: "Given I'm on the booking page, When I enter valid card details, Then the booking confirms"
3. Keep criteria focused—3–5 per story max

---

## Exercise 4: Spot the Mistakes

**Task:** Review this map and identify at least three problems:

> Activities: Login, Dashboard, Settings, API Integration, Database optimization

> Tasks under "Login": Build OAuth, Hash passwords, Cache sessions, Add 2FA

**Validation:**
- [ ] At least three issues identified
- [ ] Each issue has a suggested fix
- [ ] The corrected map would better reflect a user journey

**Hints:**
1. "API Integration" and "Database optimization" are technical, not user activities
2. Tasks should be user-facing; "Hash passwords" is implementation
3. "Dashboard" might be a place, not an activity—what does the user *do* there?

---

## Exercise 5: Facilitate a Remote Workshop

**Task:** Run a 20-minute remote story mapping session using a tool (Miro, FigJam, or Google Slides). Invite 2 colleagues. Build a map for a feature you're considering. Record the session or take screenshots.

**Validation:**
- [ ] Map is collaboratively built (not pre-made)
- [ ] Backbone and body are present
- [ ] At least one release slice is drawn
- [ ] Participants contributed to the structure

**Hints:**
1. Share the user and outcome upfront
2. Use sticky-note equivalents; color-code activities vs. tasks
3. Use a timer to keep the session focused