user-story-mapping-workshoplisted

## Purpose Guide product managers through creating a user story map by asking adaptive questions about the system, users, workflow, and priorities—then generating a two-dimensional map with backbone (activities), user tasks, and release slices. Use this to move from flat backlogs to visual story maps that communicate the big picture, identify missing functionality, and enable meaningful release planning—avoiding "context-free mulch" where stories lose connection to the overall system narrative. This is not a backlog generator—it's a visual communication framework that organizes work by user workflow (horizontal) and priority (vertical). ## Key Concepts ### What is a User Story Map? A story map (Jeff Patton) organizes user stories in **two dimensions**: **Horizontal axis (left to right):** Activities arranged in narrative/workflow order—the sequence you'd use explaining the system to someone **Vertical axis (top to bottom):** Priority within each activity, with the most essential tasks at the top **Structure:** ``` Backbone (Activities across top) ↓ User Tasks (descending vertically by priority) ↓ Details/Acceptance Criteria (at the bottom) ``` ### Key Principles **The Backbone:** Essential activities form the system's structural core—these aren't prioritized against each other; they're the narrative flow. **Walking Skeleton:** The highest-priority tasks across all activities form the minimal viable product—the smallest end-to-end functionality. **Ribs:** Supporting