User Story Mapping Language
5 exercises — Practice story map anatomy, vertical slicing, walking skeleton, release sequencing, and user story format in professional English.
0 / 5 completed
1 / 5
A team has arranged their user story map in three horizontal layers. The top layer shows high-level user activities (e.g., "Search for a course"), the middle layer shows specific tasks within each activity, and the bottom layer holds granular implementation stories. What is the correct terminology for each layer?
In Jeff Patton's user story mapping framework, the backbone holds user activities at the top and user tasks in the middle layer — the bottom layer holds the story slices that will be assigned to releases.
The backbone (activities + tasks) tells the complete user narrative from left to right: "User searches → finds a course → enrols → completes a lesson → earns a certificate." This narrative stays stable. The story slices beneath each task are what the team prioritises and assigns to releases — a horizontal line divides what's in scope for Release 1 from what's deferred. This structure prevents the team from losing sight of the user narrative while breaking work into deliverable chunks.
Key vocabulary:
• backbone — the top two layers of the map showing the user narrative; typically stable across releases
• story slice — a granular implementation story beneath a task; what gets assigned to sprints
• release line — a horizontal cut across the map separating stories included in a release from deferred ones
The backbone (activities + tasks) tells the complete user narrative from left to right: "User searches → finds a course → enrols → completes a lesson → earns a certificate." This narrative stays stable. The story slices beneath each task are what the team prioritises and assigns to releases — a horizontal line divides what's in scope for Release 1 from what's deferred. This structure prevents the team from losing sight of the user narrative while breaking work into deliverable chunks.
Key vocabulary:
• backbone — the top two layers of the map showing the user narrative; typically stable across releases
• story slice — a granular implementation story beneath a task; what gets assigned to sprints
• release line — a horizontal cut across the map separating stories included in a release from deferred ones