StoryMap Tree

Storymap Tree

All stories, issues, milestones etc. in Agemba are organized in the  Storymap Tree. You can view and maintain the tree structure in the Storymap view (tree is shown as cards top-down) or in the Outline view (tree is shown as an indented list tree).

The Storymap Tree has four main branches from the top of the circle:

The “Why” section

Includes ideas and issues, impediments and improvements

Ideas and issues are often based on direct input from users. More users may have reported issues, that are partly overlapping. Or they may come up with similar ideas explained from different user perspectives. 

The entities can be organised below a tree of the corresponding epics. One grouping could include issues from a specific customer or ideas from a user event. Or ideas could be grouped depending on the type of idea addressed.

Issues and ideas in the “Why” section will often be implemented by stories in the “What” section, see description of an Implemented Relation. They can also be planned directly to a release or sprint.

The “What” section

Includes stories and infrastructure stories. 

Entities in the “What” section are also organised in a tree structure, where epics may contain other epics. Stories are the leaves of the tree. At the top of the “What” subtree, epics can be grouped into themes.

Epics are not just for grouping. Like stories and ideas etc., epics also has a user story text.  If a user story is too big (in effort time) for a sprint, you should create an epic. Below the epic you can detail the user story of the epic into smaller stories. Implementing all the stories below an epic means that the epic is implemented.

The stories in the “What” section are typically more concrete and “worked through” than the ideas in the “Why” section. In an organised way, they describe “what” is going to be features in the product. As mentioned above, stories and epics may implement issues and ideas from the “Why” section.

Infrastructure stories are basic features described in a more technical way. Ordinary stories and epics will often depend on these to be finished first, see the description of Dependency Relations

The “Who” section

Includes User Personas.

You can create a User Persona to represent a customer, an internal group or any other person or group. You can then create e.g. Interest Relations from this User Persona to epics or stories.

This makes it easy to keep track of the stories, which e.g. a customer has an interest in.

The “When” section

Includes Milestones, Releases and Sprints.

The “Inbox” and “Heap”

See Inbox and Heap overview.