story-mapping-the-solutionlisted

# Story Mapping the Solution ## Overview A user story map (Jeff Patton) replaces a flat, context-free backlog with a **two-dimensional narrative**: what the user does, end to end, sliced into releases that each deliver a complete journey. Use it after discovery has established *what's worth building*, to shape *how it ships*. ## Structure - **Backbone (top):** large **user activities** — the essential things people do — arranged **left-to-right in narrative/time order** (the order you'd explain the system in). - **Body (below each activity):** smaller tasks/stories hanging down, ordered **vertically by necessity** (most necessary at top). - **Walking skeleton (top slice):** the highest stories across the whole backbone form the **smallest possible end-to-end system** (Cockburn: "a tiny implementation that performs a small end-to-end function… links together the main architectural components"). - **Release slices (horizontal):** each release spans the **whole backbone** so every release is a complete, usable journey — you slice *across* the narrative, never building one activity to completion while others are empty. ## Workflow 1. Build the backbone: list user activities, order them left-to-right by narrative flow. 2. Hang the detail: place tasks/stories under each activity, highest = most necessary. 3. Cut the walking skeleton: the top row that gives end-to-end functionality across every activity. 4. Slice releases horizontally; each slice must span the full backbone.