Factors from outside the scope of the work going on in a Circle such as The Law or company mandate often change and may require that some items of the …

An ordinary milestone is reserved for the product owner to use for establishing milestones based on his/her own preferences.

Contrary to the Delivery In milestone, this is intended for use when setting milestones for specific story map items that are to be delivered to an outside party within a …

Infrastructure Epics are larger stories. In the Storymap Tree you can have as many levels of epics as you like to describe the project. Once you reach a level which cannot …

A story contains a user story (user request). User stories are descriptions of a feature told from the perspective of the person who desires the new functionality.

A theme should ideally be used when an infrastructure to be added to the Storymap is in its broadest form. For instance in a website implementation project example, the item …

Issues in Agemba describe errors or disadvantages associated with the ongoing work in the Circle. This card enables you to add identified issues as its children where they can then be resolved either directly or indirectly by a story or an epic.

New input to the initiative in focus e.g suggestions for changes or new modules should be operated as children of this card.

While the team is in progress with a sprint, it will often encounter impediments that are obstructing it from achieving sprint goals. In Scrum, the role of identifying…

Any new input to the work going on this Circle that is considered as an improvement should be operated as a child of this card; either as a story or an epic depending on how broad it is.