Matrices, tables and analysis panels
Story map
A story map: user activities across the top, stories beneath, releases sliced horizontally.
matrix.storymap@1New DDN source
Why use it?
It keeps the walking skeleton visible while the backlog grows.
When it helps
Release planning for a user-facing product.
How to read it
- Top row is the user's day; below is what we build, sliced by release.
- A story above the release line ships; below it waits.
What you need
- The activities
- The stories under each
- The release slices
Things to check
- Do not slice releases by component — slice by user outcome.
- Do not let the top row become a feature list.
Scope of this diagram
Declared map content; no estimation or velocity is computed.
Work with the converted example
- Open the viewer and select
storymap. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.