# User Story Mapping — Quick Reference

## Backbone vs Body

| Part | What It Is | Example |
|------|------------|---------|
| **Backbone** | High-level activities, left-to-right (top row) | Browse → Add to cart → Check out → Track |
| **Body** | Tasks under each activity (stacked below) | Under "Check out": Enter shipping, Choose payment, Confirm |

## Building the Map

1. **Identify user** — Who is this for?
2. **List activities** — Verbs, left-to-right
3. **Add tasks** — Under each activity
4. **Order** — Natural user journey sequence
5. **Walk the map** — Read as a story; find gaps

## Slice Releases

| Slice | What It Means |
|-------|---------------|
| **Release 1** | Above the line—walking skeleton (MVP) |
| **Release 2+** | Below the line—later iterations |

**Rule:** Slice horizontally. Most important tasks at top of each column.

## Walking Skeleton

The thinnest end-to-end path that delivers user value. Minimum tasks to complete the journey.

## User Story Format

```
As a [user], I want to [task] so that [outcome].
```

## Acceptance Criteria (Given/When/Then)

```
Given [context], When [action], Then [expected result]
```

## Workshop Checklist

- [ ] Define user and outcome upfront
- [ ] Activities = user actions (not features or screens)
- [ ] Include developers, designers, product
- [ ] Walk the map to validate
- [ ] Vote or discuss to prioritize tasks
- [ ] Draw the line: above = Release 1

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Too granular too early | Start with activities + few tasks; add detail when slicing |
| Forgetting user goal | Tie map to specific user and outcome |
| Activities = features | Activities are user actions (e.g., "Compare products") |
| Skipping the walk | Read map left-to-right; gaps will appear |
| One map for everyone | Different users → different maps |

## Map → Stories

Each task can become one or more user stories. Add acceptance criteria. Treat the map as a living artifact—update as you learn.