part two · story mapping

Story Mapping

Epics as columns, stories as rows, releases as slices.

A story map is the team's two-dimensional drawing of the work. Time goes left to right (the activity sequence). Detail goes top to bottom (the breadth of stories within each step). Releases are horizontal slices through the map.

The story map is how the trio negotiates which stories ship together — a question that cannot be answered from a flat backlog.

The shape

Activity flow →
─────────────────────────────────────────────────────────────
| EPIC 1            | EPIC 2            | EPIC 3            |
| Sign in to start  | Open today's      | Grade the         |
| the day           | grading queue     | morning batch     |
─────────────────────────────────────────────────────────────
| Email login       | Queue loads       | Open submission   |  ← walking
| Forgot password   | < 2s              | Score the rubric  |    skeleton
─────────────────────────────────────────────────────────────
| Magic-link login  | Queue filters     | Add written       |  ← release 2
| MFA               | Queue search      | feedback          |
─────────────────────────────────────────────────────────────
| SSO via SAML      | Custom queue      | Bulk grading      |  ← release 3+
| Session sharing   | views             | shortcuts         |
─────────────────────────────────────────────────────────────

The top row is the walking skeleton (Part 3) — the smallest story per Epic that, taken together, makes a complete activity. Below that, releases get progressively richer. The bottom of the map contains stories that may never ship — they are the candidates the trio is willing to consider but has not yet decided on.

How to draw the first version

Anchored to the Epic Kickoff (Part 1) outputs and the journey map (Volume II Part 3).

1. Draw the Epic columns left to right, in journey order.
2. Under each Epic, list the candidate stories from the kickoff's backbone.
3. Sort each column top to bottom by minimum viable down to would be nice.
4. Draw the first horizontal cut — the walking skeleton — across the top of every column.

The cut is the discussion. The trio negotiates which stories make the cut. The discipline: every Epic must contribute at least one story to the walking skeleton, or the Epic does not belong in this release at all.

Releases as slices

A release is a horizontal slice. The slice is shipped together — the cohesion is what makes it useful. Shipping half a slice is shipping nothing.

The corpus pattern: name releases. Walking skeleton, Release 2 — graders can do their day, Release 3 — graders can move faster. Named releases are easier to defend in conversations with leadership and clients than numbered ones.

What the map is for

Three jobs.

1. Negotiate scope without a backlog. A backlog is a list of every story ever proposed. A map is a curated arrangement that shows trade-offs.
2. Make the walking skeleton visible. The horizontal cut at the top is the team's commitment for the cycle.
3. Surface gaps. An Epic with no candidate story is a gap that the kickoff missed. An Epic with too many candidate stories is one that the trio has not yet thought hard enough about.

What the map is not

Not a Gantt chart. Not a roadmap. Not a backlog substitute. The map describes what could ship together and what is in the next slice; it does not describe when.

When-questions go in the release plan, which lives next to the map but is a separate artifact.

Updating the map

The map is updated:

• After every Epic kickoff (new stories surface).
• After every retrospective (priorities shift).
• After every signal reading (predictions either confirm or surface new stories).
• After every postmortem with structural implications.

A static story map is one that is no longer being used. The map is meant to evolve as the chain learns.

Part 3 — Walking Skeleton →