- Milestone Relation
If you add a relation from e.g. an epic to a milestone, it means that the epic must meet the deadline of the milestone.
You can have relations to milestones from: stories, issues, ideas, impediments, improvements, notes, epics and themes.
- Release Planning Relation
A relation from e.g. an epic to a release means that the user story described in this epic will be part of the release.
You can have relations to releases from: stories, issues, ideas, impediments, improvements, notes, epics and themes.
- Sprint Planning Relation
A relation from e.g. a story to a sprint means that the user story described in the story will be part of this sprint backlog. A sprint is always part of a release, so the story will also be part of this release.
You can have relations to sprints from: stories, issues, ideas, impediments and improvements.
- Preplanning Relation
A relation from e.g. an epic to a preplanned list means that this epic is not yet planned to a release but merely “preplanned”. Preplanned lists are for grouping the epics in what might become a release with a specific release date. It is for ordering epics and emptying the list of unplanned stories shown in the left pane of the Product Backlog.
- Milestone Relation
Note that you cannot have a relation from a theme, epic or note to a sprint. The typical way to work is that you drag an epic to a release in the Product Backlog window. Before and during the sprint planning, you detail the epic into stories. You then add the stories to the sprints.
If an idea is implemented by a story, it means that the story “includes” the idea during the implementation and during the planning. The idea is not planned to a release or sprint by itself but via the story.
You can still see the state (Created, Done etc) on the idea card, but it will to some extend mirror the state of the implementing story. So if you set the state of the implementing story to “Done”, it should mean that the story and the ideas, it is implementing, are all done.
It is always an entity in the “What” part of the Storymap Tree (story, infrastructure story or epic) that implements an entity from the “Why” part of the Storymap Tree (issue, idea, impediment, improvement or the corresponding epics).
The “Dependency” relation means that a:
- Story or epic
waits for an:
- Infrastructure story or infrastructure epic
to be completed, before it can be completed.
Interest to Relation
An interest relation can be setup to describe that a given functionality is of interest to a user persona. This is primarily for categorizing stories according to user personas and will not have any impact on the workflow.
How to see a relation in Agemba
All non-planning relations are shown in relations tab.
In the Storymap view you can see the relation as a line between two cards (e.g. between a story and a sprint card). In the Product Backlog sprint you will just see the story in the release or sprint box.