The Story Map is a graphical view showing the functional structure of the Circle and the relationships and dependencies between epics and stories in the Circle.
The Story Map tree-structure depicts the “what, why, who and when” of everything that happens in the Circle. Items are shown in functional groups and include everything from broad themes and developing ideas down to specific issues and stories in progress.
The Story Map encourages the user to break-down Epics into a set of smaller, ordered Stories – with increased level of detail for each level. This hierarchical breakdown triggers geographical recognition and thereby gives a better overview.
For planning purposes stories can be linked to Milestones, Releases, Sprints, Kanban and Preplanned lists, which can also be done in the Product Backlog
Each Epic or Story is depicted in the Story Map as a Story Card identifying its title and a unique assigned id displayed on the card’s header. Other icons on the story cards indicate key properties such as its workflow state, type, planning status and value/effort estimation in story points.
All details of the Story can be seen in the mouse over or in right pane overview, including the user or team to which it is assigned, the user story and optionally a detailed description,and any relevant file attachments.
Story Workflow and Estimation
Stories pass through a number of workflow “states” on their way from being newly created and “Ready” through “In Progress” to “Done.” State changes are made manually, but automatically reflected through the hierarchy to which the story belongs. Similarly, the value/effort estimation of a story will be aggregated and summed up through the hierarchy, so that its effect on the overall endeavor is transparent to all.
Issues and Ideas
Although Issues and Ideas can be planned to Releases, Sprints or Kanban and exist independently, they can also be linked to a Story and integrated with its implementation. In the latter case, the progress of the Story is reflected in the original Issue or Idea items.
Quite often, Stories require some infrastructural things in place before they can be completed. For that, Infrastructure Stories can be created and a dependency can be created between them and the Stories. Stories with dependencies cannot be executed to completion until the Infrastructure Story’s execution is completed.
Delegation of Stories
Stories can be worked on in the Product or Sprint Backlogs of their host Circle. However, stories can be delegated to other Circles or to third party applications like Jira. A copy of the story is created in the delegated Circle or application and progress and details synchronized with Agemba. Delegated stories have the “delegation” icon displayed on their story card.
Working in The Story Map
For ease of use, large Story Maps can be maneuvered on screen and zoomed in and out. They can also be filtered to show specific sections of the tree. The tree can be restructured and story types changed. The Story Map, or sections of it can be exported to PDF.