Story map

The user journey laid out, and sliced into releases.

01What it's for

The story map lays out the user journey and slices Features into releases, starting with a walking skeleton. It builds shared understanding between Product Management and the teams.

02What it turns into on the old system

The backlog becomes a flat list of requirements, sequenced by component: first the database, then the back end, then the screens.

03How you notice

Release 1 contains everything.
Slices are technical layers, not steps in the journey.
The map is made by one person and handed over.

04How to make it work

Build it together with the teams.

Slice by user journey; start with the thinnest end-to-end version.

Use release lines as learning milestones, not as delivery dates.