How to get data from spreadsheet to Agemba?
This is an easy way to create a list of stories, epics, folders etc in Agemba based on data from a spreadsheet.
First you need to describe the stories in a spreadsheet (e.g. Google Docs or Excel). The first line must contain the property names and the lines below must contain the data.
|story||Do some work||As a user I would like…|
|story||Some other work||As a user I would like…|
Then copy the lines in the spreadsheet to the clipboard.
In Agemba select the “Import Children From Clipboard” menu entry for e.g. an epic or a folder.
The following window is opened. Here you can validate the data.
If you want to change the data before activating the import, you can modify the data in the spreadsheet, copy it to clipboard again and click on “Refresh from Clipboard” to update the data.
When you click on “Import to Agemba”, the stories are created in Agemba.
Which Item Types can be imported?
You can specify the following types: Story, Epic, Infrastructure Epic, Infrastructure Story, Idea, Issue, Objective, Risc, Note, Folder, Task, Release, Ordinary Milestone, Deadline Milestone, Delivery In Milestone, Delivery Out Milestone and User Persona.
If you do not specify the type, the type will depend on the parent. If you import an item below an epic or folder in the What area, the default type is Story. If you import an item in the Feedback folder, the default type is Idea.
If you do not want to specify the type, but still want to see the selected type before import, add an empty ‘type’ column. The selected type will then be show in the import window.
Which Item Data can be imported?
The only column, you have to specify, is the “title” column. It must have a value for all rows.
The following are some of the data, you can import. Use property display title or system name (the name in parentheses):
- Type (type)
- Title (title)
- User Story (userStory). Only plain text – i.e. no rich text as e.g. images and links.
- Detailed Description (detailedDescription). Only plain text – i.e. no rich text as e.g. images and links.
- Required When (storyWhenDate). Dateformat: YYYY-MM-DDDD
- Kano (kanoClass). Values: Exciter, Indifferent, MustHave, Reverse, Satisfier
- Expected Value (bValueExpected)
- Worst-case Value (bValueWorstCase)
- Cynefin (effortCynefin). Values: Chaos, ChaosObvious, Complex, ComplexChaos, Complicated, ComplicatedComplex, Disorder
- Expected Effort (effortExpected)
- Worst-case Effort (effortWorstCase)
The data will only be added, if the requested type can have this kind of data.
How to import hierarchy of Items
If you want to import a hierarchy of items – e.g. an epic with stories – you must add the Level column. If you add the Level column, it is mandatory to include the Type info on all rows as well.
|1||epic||First epic title||As a user I would like…|
|2||story||First story in epic||
As a user I would like…
|1||epic||Second epic title||
As a user I would like…
In this example the story is placed below the first epic in the Storymap.