Read more about the general principles of Cost estimation here. If the story is delegated to another circle and cost is configured to automatically synchronize, then the displayed cost will …

Read more about the general principles of Value estimation here. If the story is delegated from another circle and value is configured to automatically synchronize, then the displayed value will …

When creating a new circle you can choose whether you want to be added as managing user in this circle or not. If you intend to add another user as circle manager after creating the circle, you can deselect this option.

As a Site Administrator you will still be able to access a circle, which you are not explicitly a user in, including editing users. But you have to be a managing user to create stories etc in the circle. You can at anytime add yourself as a user to any circle in your site.

Add an existing Jira Issue, that is within the same Jira Project as the one the Agemba Circle is configured to sync with, as a new item here. The Jira …

Adding Users To Circle Existing site users can be added to a circle without sending an invitation. Simply search and select the user you want to add; select a circle …

mainhelp_freebie

Here is the excerpt

When you have been invited to to Agemba, you first need to create a user profile. Only password and username are mandatory. First/last name, telephone and user profile image are …

Welcome to Agemba Since you have access to multiple sites, you first need to select a site using the site selection dropdown in the top menu.  You can read more …

Agemba-Jira integration What does integrating Agemba with Jira mean? The whole idea behind integrating Agemba with Jira is simply to allow strategically organized work (Stories) in Agemba to be delegated …

The Agemba Main Menu The main menu gives you access to the different windows related to the current Site and Circle. You can see the name of the current Site …

The All Recently Edited list shows all stories in the Circle – no matter if you are following them or not

Cancelling delegation on an epic/story will completely remove it from the circle that it’s delegated to, terminating the delegation process.

A circle is a unit within the organization containing one roadmap and one product backlog.

The Circle Activity feed shows all (direct) changes made or comments written within this circle.

Circle Map The circle map is for organizations who wish to have more than one scrum team, where each team has their separate Product Backlog. You can have one or …

The manifest is a rich text field that can be used to for example state the purpose, terms and function of the delegation relationship between the Circles or for any other purposes. Files in the form of pictures, PDFs etc., can be attached to this region too.

A user can have a direct circle role (as opposed to indirect roles via team membership) which determine his user rights

This section, allows for customization of the functional features that will be available in the Circle. It is meant to assist the user in freely choosing the features they need …

Circle Users List In this list you can see all circle users and their details, including circle roles and team memberships. By right-clicking on a row in the list, you …

Quick access to write a comment

It is possible, for each circle, to configure exactly which parts of Cost estimation are relevant. Read more about the general principles of Cost estimation here. When you change estimation …

It is possible for each circle to configure exactly which parts of Value estimation are relevant.  Read more about the general principles of Value estimation here. When you change estimation …

Read more about the general principles of Cost estimation here. If the alh-replace:typestory/alh-replace is delegated to another circle and cost is configured to automatically synchronize, then the displayed cost will …

The cost of completing a story can be estimated both in terms of the amount of effort (aka work) and in terms of money. The primary objective of estimating cost …

Has no effort estimate The effort estimate has not been set. Effort estimate is too high A max recommended effort estimate threshold is defined for the circle (read more here). …

Current Site and Circle In the main menu, you can see the Site and Circle, on which you are currently working (marked with red in the figure below). In the …

The icon located at the top right corner of the Dashboard view gives access to the facilities for customizing Dashboards. Site Administrator or Circle Leadership users can create and maintain …

The icon located at the top right corner of the List view gives access to the facilities for customizing lists. Site Administrator or Circle Leadership users can create and maintain …

The Cynefin framework was developed by Dave Snowden & Cynthia Kurtz from 1999 to 2005. It is used to describe problems, situations, systems and leadership. By offering a thinking-model, a …

The Dashboard is a multi-page, customizable view which can be personalized with “dashlets”  to show precisely the information required to orient the user and establish the priorities. Unless configured, it …

Site and Circle Dashboards Agemba has two dashboard windows, one at site level and one at circle level. You can access the Dashboard window from the Main Menu. What is a …

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 …

A Deadline is a date, where the alh-replace:typestory/alh-replace needs to be finished. A Planned date is a date, where the alh-replace:typestory/alh-replace is planned to be finished. If there is a …

This viewbox shows the deadlines for a story or epic.

Delegate this item to another circle. Please read more about the general principle of delegation here. Relations between circles in the Circle Map determines, to which circles you are allowed to delegate.   …

Delegating an Agemba Story to Jira will result in the creation of a Jira Issue with a similar title and description composing of a merge of the user story and …

You can create an epic or a story in one circle with the initial user story and then delegate the epic/story to another circle for further refinement and implementation. The …

This denotes the direction in which delegation of Epics or Stories is allowed to take place between the Circles in question

This region displays information about the delegation setup between the Circles i.e whether delegation is only possible one way or both ways. It also displays any items that have been delegated between the Circles. Clicking the delegated items will open a list of the same in the List View.

Cost estimation and Value estimation can be synchronized for delegated stories. Whether or not cost and value is kept in sync is configured for individual circle relations. It is thereby …

Deleting will remove the item and put it in the trash. Deleted items can be restored

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 …

The user story should describe the requirement from the user perspective. The Detailed Description is for further explanations and details.

Show epic/story card in StoryMap left pane as a tree with children and dependencies. Detail plan the stories from the left pane by dragging stories to sprints.

Shows information entered or set in the circle, where this epic/story is delegated from. The “Shareable link” opens a new tab with the epic/story in the circle delegated from.

This will disable dragging of this particular Roadmap item, while in this view.

Kanban lane configuration allows for 3 main actions i.e.  Adding columns (sub-states) to the lane. Adjusting the wip limit (max number of items) per column. Except for the To Do and Done columns, reordering …

…

Plan the story/issue/epic directly to a release, sprint or kanban lane by selecting the release and possibly sprint or kanban lane name. Note that epics cannot be planned to sprints or kanban lanes.

The releases, sprints and kanban lanes are usually created and planned from the Product Backlog page. So the values available in the selection lists depends on which planning containers (releases etc.) have been created.

Preplanning containers are also created at the Product Backlog page. Use these containers to group stories etc. which are not yet ready to be planned for a release. When the story is planned to a release, it will be removed from the preplanning container.

Write the email of the person you wish to invite to the Site or Circle.

Disabling Objectives means that Objectives and Risks can neither be defined nor applied in the Circle. However any existing ones will not be removed but silently ignored and hidden out …

Dragging of Item cards shown on the Roadmap will by default be disabled and can be enabled by clicking on this menu item.

Disabling Feedback will disable the feature of Creating and working with Issues and Ideas in the Circle. Any existing Issues and Ideas will be silently ignored and kept out of …

Disabling Notes will remove the possibility of working with Simple Notes in the Circle. Information on existing Simple Notes will however be preserved.

Disabling Preconditions will consequently disable the feature that enables working with Precondition Epics and Stories. Information about any of the existing Preconditions will however, be preserved. 

Disabling the Roadmap will remove the possibility of working with a Roadmap in the current Circle. If there was an established Roadmap however, and some items were planned in it, …

Disabling Stakeholders will consequently disable the feature that enables incorporating Circle stakeholders in the form of personas. Information of existing personas will however be preserved and not removed completely.

The options here include enabling working with either Sprints or Kanban Lanes, or together, or even with neither one of them. When disabled, the Circle will exclude a Tactical Backlog …

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 …

In Agemba it is encouraged (but not mandatory) to take uncertainties into account when estimating effort and value. This is done by setting not only one single estimate for the …

This is a folder/category that allows for organizing input from customers or product/service users in the form of Ideas or Issues. These can be created directly under this folder or …

Select if you want to follow/unfollow changes on behalf of your teams(s)

Select if you personally want to follow or unfollow changes

The Followed by Me list shows all stories and other items which you have chosen to follow (not including those items which your team(s) follow)

The Followed by Me list shows all stories and other items which you have chosen to follow (not including those items which your team(s) follow)

The Followed by Me or My Teams list shows all stories and other items which you have chosen to follow personally or is follow by your team

The Followed by Me or My Teams list shows all stories and other items which you have chosen to follow personally or is follow by your team

In Agemba you can manually choose which items are of special interest to you and you therefore wish to follow changes made to them.

The Functional (What) Folder, focuses on what the strategies or ideas for solutions are? How do they contribute to the values desired? What are their costs and risks?

This is a folder that allows creating and grouping Epics, Stories, Ideas or Issues depending on where the folder resides.

Ideas can be both concrete suggestions as well as more vague comments about how end-users see the product/outcome of the project. They could for instance be the result of a …

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.

The Inbox is where new Stories (and Issues/Ideas or impediments/improvements) are put when created from the main menu.

To invite a user, write his email address and select roles/teams

Inviting a User to the Site To add a new user to the site, you need to enter and invite the person by email address. The invited person then receives …

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.

In this tab you can configure a Jira connection.

This story has been delegated to a Jira project.

If you click on the Issue Key link, the Jira task connected to this story, will be opened in Jira.

This is a container for Kanban.  Items, which primarily include Stories of the different available types, can be added via drag and drop from Preplanned lists, Releases, Spints and generally …

This is card that represents a Kanban Lane in Agemba.

This a folder that allows for creating one or more Kanban Lanes. 

A Kanban lane is a workflow line consisting of sub-states (sub-queues) each with their own done-criteria and each serving as the input queue for the next state. By default it …

Kano classification is a theory and principle for evaluating customer satisfaction, originally developed by Professor Noriaki Kano in the 1980s. The exact terminology differs in different presentations of the classification …

In the list view you can see all items, search and sort

Move this entity to a different place in the StoryMap tree. This may require a type conversion.

Change state of entity. Set this state, if the story is not relevant (at least for now).

Changes the state. Means that you want to start preparing the entity.

Changes the state. Means that the entity has been described and is ready for implementation.

Go to Outline and show this entity in tree.

Go to Storymap and show this entity in the Storymap tree.

The milestone specifies a deadline. Epics and stories can be linked to this milestone to indicate that they must meet the deadline.

Moving an epic/story to another circle will completely remove it from the current circle and create an identical one in the selected circle.

The personalized Activity feed shows all changes made or comments written within the site or circle, that are relevant for the user currently logged in.

Filtered lists of all the entities that the currently logged in user is a part of, has been assigned to or is a member of a team that has been assigned or has comments they/their team are/is mentioned in.

Notes are meant to be used in the first draft planning.

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

Outline View In the Outline view you see the Storymap Tree as an indented tree list for the Functional (What) and Feedback Folders.  An adjustable timeline is incorporated, plotting Releases …

This region displays any planning information of the current entity, which can be what Release, Sprint, Kanban it is planned to as well when it is Preplanned.

Precondition 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 …

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 Preplanned list is an ordered list of product backlog items that are yet to be explicitly planned. Preplanning stories/epics is to obtain an early grouping of items for a future release.

This is the container that represents a Preplanned list. Items, which primarily include Stories of the different available types, can be added via drag and drop from Releases, Sprints, Kanban …

This is a folder/category that allows for creating one or more Preplanned Lists. See what a Preplanned List is here.

Checking this box will disable the possibility of dragging this item from its current position on the Roadmap. To re-enable dragging, simply uncheck and save the change.

In the Main Backlog you can plan the backlog items and add these to releases and sprints.

In the left pane of the Product Backlog window you can see the Stories, Epics etc. from the Storymap Tree, which have not yet been planned for a release or …

   Planning Relations In Agemba you can create the following planning relations to milestones, releases, sprints and preplanned lists. Milestone Relation If you add a relation from e.g. an epic to …

A Release is a special type of Milestone. It is the base for the planning in the Product Backlog.

This is the container that represents a Release  Add and remove Epics and Stories Items, which primarily include Epics and Stories of different types, can be added via drag and …

Removing a lane from the roadmap will remove it permanently and all the items in the lane will be removed from the roadmap

If you want to check out agemba before deciding on whether to buy a license, you can get a freebie version. In this version you will be able to check …

Open Right-Panel Details Window From some of the main windows (StoryMap, List etc.), you can open and close a “details” window by clicking on the  icon at the right side border …

This is a card that represents a Roadmap where one or more Roadmap Lanes can be created and managed.

The Roadmap is a high-level overview of milestones and steps. It gives you a starting point for your initial planning as well as a top-level view of the progress. The …

This is a card that represents a Folder where one or more Roadmaps can be created and managed.

Quick overview of relations and planning by overlaying card

To complete the request for a freebie version of agemba, you have to fill out details needed for creating a user profile and a freebie account (aka site) and project. …

Go to Product Backlog and show this entity in left pane.

Go to Sprint Backlog and show entity in left pane.

A site is an organization account.

A user has a site role which determine some of his user rights

In this tab you can see a list of all users and their details, access to manage user rights and invite new users.

A Sprint is a time-box during which a “Done”, useable, and potentially releasable product/service increment is created.

Tactical Backlog View The Sprint Backlog view is a daily tool for the sprint team to keep track of the sprint progress. Stories with the highest priority have been added …

In the left pane of the Sprint Backlog window you can see the stories, epics etc. from the Storymap Tree, which have not yet been planned for a release or …

A Sprint is a container of a set of Items for delivery that have been agreed to during Sprint planning by the Team and the PO. Add and remove Stories …

A Sprint is a container of a set of Items for delivery that have been agreed to during Sprint planning by the Team and the PO. It typically has three …

Stakeholders (Who) – Focus on who the beneficiaries are? Who will benefit from this? Who will use this and achieve value?

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.

The selectors here provide a way to plan the epic/story to a Release, Sprint, Kanban Lane or to Preplan.

Note that only the “direct” planning is specified here. The epic/story may be “indirectly” planned to a release,, e.g. because a parent epic or all the children are planned to the release. Please see the planning state in the overview tab.

In the Storymap view, all the items in the Storymap Tree are shown top-down, starting from the Circle. You may choose to show only part of the tree by selecting …

Storymap Tree All Epics, Stories, Ideas, Issues, Milestones etc. regardless of where created within an Agemba Circle will end up placed somewhere in the  Storymap Tree. You can view and …

In this tab you can add and see acceptance criteria.

In this tab you can see a log of all the changes made to the entity.

In this tab you can upload files. The uploaded files can be used from the editor.
Note: The editor area needs to be selected in order to paste any content from the clipboard.

In this tab you can see and make comments to the entity.

In this tab you can edit basic information.

In this tab you can edit basic user details

In this tab you can edit the view and edit rights of users. A user can be given different roles or be assigned to one or more teams in the circle, whereby he will indirectly get a role.

In this tab you get a read-only overview of the basic information.

In this tab you can see the user details and roles

In this tab you can see and/or add relations between entities.

alh-optional:SprintAndKanban Tactical Backlog View /alh-optional alh-optional:OnlyKanban Kanban Board View /alh-optional alh-optional:OnlySprint Sprint Backlog View /alh-optional alh-optional:SprintAndKanban,OnlySprint This view is a daily tool for the sprint team to keep track of …

A team is a collection of users. A team can be mentioned in comments and assigned to tasks.

A user can be a member of one or more teams and thereby obtain his user rights from these teams

All team members will inherit the user rights from the team(s) which they are a member of. The team role determines which user rights team members will get.

A list of all the teams in the Circle, showing their names, roles, etc

In this tab you can see a list of all teams in the circle and their circle roles. New teams can be created and by right-clicking on a row in the list, you can edit the existing teams.

In the trash bin you can see a list of all the trashed data. You can filter this data using columns filters or free text search. It is possible to …

Undelegating from Jira will completely severe the link to Jira Issue that the entity currently has.

If a subscription is no longer needed for one reason or another, this will cancel the subscription and remove this item from the subscribing Circle.

A user can have different roles and thereby have acces to view, edit or perform different tasks.

Users are invited by email. The user invite specifies the roles and/or team memberships of the user.

In Agemba there are three different user license levels: Limited, Regular and Leadership

Representations of the beneficiaries of the initiative of the Circle in form of personas.

What are User Stories (descriptions)? User stories are descriptions of a feature of functionality told from the perspective of the person who desires the new functionality. It is meant to …

What are User Stories (descriptions)? User stories are descriptions of a feature of functionality told from the perspective of the person who desires the new functionality. It is meant to …

Using the rich text editor you can format your text (e.g. a user story or detailed description) as you desire. Most of the format options displayed in the menu are …

The value of a story consists both of a value classification and a value estimate. The primary objective of estimating value should be to give a better overview for planning …

Has no Kano class The Kano class has not been set (only if Kano classification is enabled) Has no value estimate The value estimate has not been set. Value uncertainty …

When – Finally focus on the time-related constraints. When do certain things have to be accomplished? Contracts,legislation, budgetting rounds are examples of the many constraints for initiatives that appear in the time domain.

Why – First focus on the value;what values or business objectives do you want to harvest?

For planning and prioritization it can prove beneficial to distinguish between Must-haves and non Must-haves. A Must-have is a story, which is required and therefore not something which can be …

You can write your comment using the rich text editor. See a more general description of the editor here, including how to reference files, insert images and reference other stories. …

Convert entity to story.

From the Quick Action dashlet you can do the following

Description of issue. Below is an illustration of an ordinary Story, highlighting common icons displayed on cards and what they represent:

Description of task

Description of improvement

Description of impediment

Convert this entity to an Epic.

Convert this entity to an Precondition Story.

Convert to Precondition Epic.

Convert to idea.

Convert to Idea Epic.

Convert to issue.

Convert to issue epic.

Shows information entered or set in the circle, where this epic is delegated to. The “Shareable link” opens a new tab with the epic in the circle delegated to.

Find and highlight this entity.

Here is viewbox cost

Here is value estimation

Read more about the general principles of Value estimation here. If the story is delegated from another circle and value is configured to automatically synchronize, then the displayed value will …

When the alh-replace:typeepic/alh-replace is switched to accumulate value, its original value estimates are preserved and can be used to compare with the accumulated value. Read more about the general principles …

When the alh-replace:typeepic/alh-replace is switched to accumulate cost, its original cost estimates are preserved and can be used to compare with the accumulated cost. Read more about the general principles …

Cost estimation and Value estimation can be synchronized for delegated stories. Whether or not cost and value is kept in sync is configured for individual circle relations. It is thereby …