The Story Map in SwiftEASe offers you a comprehensive mapping tool to organize user stories into a visual map that communicates the end-to-end user journey from the big picture to actionable user stories. Inspired by Jeff Patton’s famous model, the three levels of the Story Map helps you to:

  • Frame the big picture of user requirements at the first or top-most level that addresses the common goal.
  • Decompose it to the smaller, epic level activities and associate them with the user persona at the second level.
  • Break the user-driven activities down into smaller building blocks or user stories and associate them with a PI strategy.

So, with the Story Map, you can quickly and efficiently build an MVP version of a product or feature in a Lean-Agile manner and achieve its desired outcomes with faster turn-around time.

Advantages of using Story Mapping

  • Helps you visualize your product roadmap.
  • Keeps the team members and the customers on the same page about what is happening on the Board.
  • Depending on the product requirements, it helps you decide the iterations for the delivery.
  • With the Multi-Board feature, you can enable multiple Boards, card types, and PI/sprints in a single Story Map.
  • It builds shared understanding and collaboration among the team members.
  • Sizing, planning, and prioritizing the workitems becomes easy.
  • You can create multiple Story Maps based on your business requirements. For example, you can create one on developing a mobile app, another for building a Chatbot.

Understanding Story Mapping

The structure of a Story Map is defined in three levels. Each level should have a unique card type associated with it.

At the top/first level of the Board, identify the Usage Sequence on how the functional flow is. These goals are divided into n number of smaller parts (for example – Epics) at the second level. Along with the epics, their personas are set at this level. You can have more than one epic and their personas at the second level of the Story Map.

Moreover, you can also enable the Multi-Board feature to configure which Work Board the cards like Epic, Feature, User Story should flow after you create them at various levels of Story Maps.

These epics are further broken down into smaller and workable parts (user stories) at the 3rd level of the Board. Once the user stories are created, planned, and prioritized, they can be tagged to their respective PI or Sprint.

For example, consider you have created two custom cards Theme and Epic and have associated them with the level 1 and 2 of the Story Map respectively. You are developing a mobile app for your eCommerce website. Its high-level goals/themes that you are planning to achieve in the next few months are ‘Find a product’, ‘Examine a product’, ‘Add to basket’, etc. These goals can be defined at the top/first level of the Story Map.

Now, the Goal/Theme ‘Find a product’ can be divided into Epics like ‘Browse product category’, ‘Search a product’, etc. At the same time, you can also define the personas of these Epics on the board like Buyer, Seller, Administrator, etc. These Epics along with their personas are set at the second level of the Board. Once you create User Stories of these Epics, you can tag them with the PI or sprints available at the PI/Sprint level of the Board.

By default, User Story is associated with Level 3 of the Board. However, you can associate any Card Type at any level.

Important Points:

Before you start using the Story Mapping Board, here are some important points you need to remember:

1. Cards Created in the Story Mapping Board Flow to Work Board

Cards created on the Story Mapping Board such as Themes, Epics, User Stories flow from Story Mapping Board to Work board. Cards created from Work board or other areas of the application are not available in the Story Mapping Board. So, it is recommended that cards are created from the Story Mapping board while working on a new feature/module.

2. Workitem’s Name, Description, PI and Sprint Flow bi-directional

When you update any of these four fields in the Story Mapping Board then these changes are reflected in the Work Board. Similarly, if you change the Name, Description, PI, or Sprint on a card from Work Board then these changes are reflected on the Story Mapping Board.

3. Level 2 – Level 3 Cards Linking  is Reflected in the Parent-Child Hierarchy View of Workitem

Linking of Epic to Theme and User Story/Technical Story to Epic/Theme done in the Story Mapping Board is reflected in the Parent-Child hierarchy view of the work item.

4. Modification in the Hierarchy View of a Workitem will not be Reflected in Story Map

The planning of a product or a feature is done in the Story Map. As the development work gets started and goes on, new workitems (user stories, technical stories, epics, etc.) may get created as the product/feature evolves. Since these workitems are created during the development and are not part of the original plan, these are not reflected in the Story Map.

So, any changes to the hierarchy of workitems made in the Story Map are reflected in the hierarchy view of the workitem but any changes made in the hierarchy view of a workitem will not be reflected back in the SM.

Besides, one may add a new level in the workitem hierarchy which is not configured in the 3 levels of the Story Map. In this scenario, workitem hierarchy cannot be in-sync with the Story Map. Also, the hierarchy may be set across multiple projects which might not be configured in the Story Map. Hence, it is recommended that you plan the product/feature roadmap in the Story Mapping Board and refer it only from the initial scope point of view. Further updates to the hierarchy should be seen in the hierarchy view of the respective items alone.


  • To use the story mapping feature in SwiftEASe, one must have the supporting license. Please contact us at [email protected] to know how to avail it.
  • You must have the Admin access to view the Story Mapping option in the Board menu and navigate to the Story Map page. Alternatively, you can also view the Story Map page provided you have the Manager access to the Board from where you are opening the Story Map.
  • The Story Map has three levels so make sure you have three unique card types defined in the project to associate with the three levels of the board.

Configuring Story Mapping screen

To configure the Story Mapping in SwiftEASe, you must enable the Story Mapping plugin. To enable the Story Mapping plugin, perform the following steps:

Note: You must have Admin or Manager access to configure the Story Mapping feature in SwiftEase.

  1. Click the Admin menu, select Admin, and select Plugins.
  2. On the Plugins page, select the Story Mapping plugin and click Enable. The Story Mapping Setup window is displayed.

3.  In the Story Mapping Setup, you can find the following details:

  • Story Mapping UI Server URL: By default, it shows the front-end URL of Story Mapping Service. like
  • Story Mapping Data Server URL: By default, it shows the back-end URL of Story Mapping Service. like
  • SwiftEase URL: It is the URL of the instance. By default, it will show the URL of the source system.
  • Admin Login ID: It is the Login ID of the Integration user for the logged-in account. This user will be used to communicate between the Story Mapping Board and SwiftEase using REST API calls.
  • Admin Password: Password of the Integration user.  Generally, you only need to enter this information in this setup dialog box.

Navigation for Story Mapping Board

To open the Story Map, select the Story Mapping option from the Board menu.

Story Map page

The first time you navigate to the Story map page, you can see a default Story Map, named Default Board. If you are visiting the Story Map for the first time, the Default Board will have nothing in it. You can start building that default Story Map Board by setting its configuration, adding cards in it, and enabling the Multi-Board feature (if required).

Many a time, having one Story Map is not enough. Your business or functional requirement mandates that you have a separate Story Map for a separate product or feature roadmap. For example, on one hand, you want to build a mobile app similar to your web application, on another hand, you want to build the Analytics feature for your application. Both of them require a separate product journey involving different personas, a different set of Epic-Theme-User Story, and may also be tracked in a separate PI and Sprints. So, for such varied requirements, it is important that you create separate Story Maps, and not just one.

To fulfill such requirements, the Story Map feature lets you create any number of Story Maps and track a separate product or feature development.

To create another Story Map, perform the following steps:

  1. Click the Add Story Map button on the Story Mapping page.
  2. Enter the Name and Description of the Story Map and click Save.

3. The newly created Story Map is displayed in the Story Mapping list.

You can modify the name and description of an existing  Story Map by clicking the Edit icon against it under the Action column. Similarly, you can delete an existing Story Map by clicking the Delete icon ,

Note: You cannot delete the Default Board.

Once you create a Story Map, click its name to open the Story Map and start building it.

Let us get to know more about it from the following sections. We will begin with understanding the layout of the Story Map which is in a Board format.

Story Mapping Board Layout

The Story Mapping Board has the following sections.

  1. Toolbar
  2. Level 1
  3. Level 2
  4. Level 3


The toolbar in Story Mapping Board helps you perform the given operations

Zoom level – As the name suggests, Zoom level helps you get the better visibility of the cards (with their ID and name) on the board.

Add Card – It helps you create a new card on the Board. To create a new card on the Story Mapping Board using the toolbar, perform the following steps-

  1. Click the Add Card
  2. Select the card type that you want to add.  Depending upon the selected card type (and the level it is associated with), the level of the board opens in a pop-up window showing the position of the columns. The columns that are already occupied are shown in a dark shade while the available spaces are shown in light space.
  3. Select the column or position of that card on the board.
  4. Click Next. The Card details pop up window appears.
  5. Enter the card title, description, and select the PI and Sprint for the Card.
  6. Click the Save button.  The card is saved successfully in the selected locations.
    Note: The card created in Story Mapping board will also be shown in the Work board and they can only be deleted or modified from the story mapping board only.

Notification – It shows a notification if any update or synchronization of information between Story Mapping Board and Application is failed.

Full-Screen view – The Full-screen view helps you see the Story Mapping board in full screen.

More  – The More icon has the following options in it-

  1.  WBS On/Off – WBS stands for Work Breakdown Structure. So, when you click the WBS On/Off toggle, it shows you the WBS code on level 1, level 2 and level 3 cards along with their ID and Name. It helps you to know the linking between the cards at the three levels.
    Note: The WBS code is shown on level 3 cards only if they are linked to level 2 cards.
  2. Layout Editor – The layout Editor helps you add a new column or delete an existing column in level 1 of the board. To add a new column or delete an existing column –
    1. Click the Layout Editor A small toolbar appears on each column of the level 1 excluding the column 1.
    2. Click the Insert 1 Column left, Insert 1 Column right and Delete Column to add or delete an existing column. The column is added or removed.
    Note: You can’t delete a column if it has cards in it. Only an empty column can be deleted.
    3. To go back to the board view, click the Back to Board button on the Toolbar.
  3. Refresh – It refreshes the Story Mapping screen.
  4. Setting – It helps you set cards at the three levels, set personas at the second level and select the option (PI or Sprint or both) that you want to tag cards to at the third level.

To do the settings of the Story Mapping Board, click the Settings icon on the toolbar. The Story Mapping Settings dialog box appears with the following sections in it-

  1. Associate Card Type to Levels – In this tab, you can set the cards to be used at the three levels of your board. It enlists all the card types that are defined in your Work board including the custom cards. Once you select a card type for level 1, it won’t be shown for level 2 and level 3. Similarly, the card type selected for level 2, won’t be shown for level 3. You can associate more than one card type for any level of the board.

To select a card type, click its name under the bar of that level and similarly, to remove a selection, click another card type and deselect the previous one.
Note: Each level must have at least one card type associated with it.

After selecting the card type for all the three levels, click the Save button or click the Reset button to reset the settings.

  1. Define Persona – This tab helps you define personas of your project at the second level of the Board. You can set multiple personas at this level (each row having a unique persona). By default, there are two personas on the board.

To set a persona, click the Define Personas tab in the Story Mapping Settings dialog box and enter the following details-

    1. Icon – Contains the profile pic of the persona. You can either select from the given icons by clicking the drop-down icon or upload an image from your system by clicking the image and selecting the Attach option.
    2. Name – Enter the name of the persona which will be shown on the board along with their profile picture.
    3. Persona – Enter the persona like Buyer, Seller, and so on.
    4. Position – Shows the position of the persons in the Story Mapping Board. For example, if persona Buyer is in the first row and persona Seller is in the second row of the board then their positions is 1 and 2 respectively. You can change the position of the persona by simply dragging and dropping them using the drag- drop icon in the left corner of the row. On reordering a persona, all its cards move along with the persona. For example, if persona Buyer has three Epics in its row then on moving the Buyer persona up or down will also move its three Epics with it.
    5. Abbreviation – Short name for the persona. For Example, for Buyer, you can set Buy, for Seller, you can set Sel etc.
    6. Description – Short description of the personas.
    7. Action – Contains two icons Save and Delete. As the name suggests, the Save option helps you save the detail of the persona you have entered and the Delete option allows you to delete the filled details.

After saving the details of the persona, click the Save button at the bottom of the diagram.

  1. Roadmap Planning – It helps you set the PI or Sprint or both for the Story Mapping board.
    1. PI – Select this checkbox to show all the open PI. You can tag a card to this PI on the Story Mapping Board.
    2. Sprints – Select this checkbox to show all the open sprints. You can tag a card to the Sprint on the Story Mapping Board.
    3. Recommended – It will show both PI’s and sprints on the mapping board. You can tag a card on the board to the given PI and sprint.
    Note: It will show all the open PI’s and sprints that are created from the top-level Board. Moreover, PI Planning and Sprint Planning plugins should also be enabled.

After selecting the required checkbox, click the Save button to save the changes.


At this level, the Usage Sequence (on how the functional flow of the project will be) is defined. This usage sequence is broken down in detail in the rest of the two levels of the board.

In level 1, one column can have only one card. The cards at level 2 which are placed in the column under level 1 card are automatically linked to it. The stretch of a column in level 1 is considered before the next card in the same row. For example, if there is a card in column 1 and another in PI and Sprint Planning column, then until you add any cards in column 2 and 3, they are considered a stretch of column 1’s card. So, all the 2nd and 3rd level cards in column 1, 2 and 3 are considered as column one.


The functional flow of the Board at level 1 is broken down into smaller parts at level 2 so that they can be tracked and managed easily. The cards at this level are associated with their personas. You can define more than one card type at this level and add cards accordingly. You can also move the cards to any column you want or link them with the cards at level 3.

By default, there are two personas on the board. You can add more personas as per your requirement from the Story Mapping Configuration Box. The Personas at this level can also be reordered along with their cards.

You can apply the zoom option specific to each level.

You also have the toggle option to Hide or Unhide empty rows in the level. It helps you to have a clear view of all the cards on each level.

Note: Once you enable the toggle option to hide empty rows, the entire row gets hidden and you won’t be able to view the rows having no cards. To check the rows with no cards, you need to disable the toggle option to unhide empty rows.


The granular level cards defined from the level 2 cards are set at this level of the board. You can set more than one card type for this level. These cards can be linked to level 2 cards which are already linked to level 1 cards and can be moved to any column across level 2 cards.

You can apply the zoom option specific to each level.

You also have the toggle option to Hide or Unhide empty rows in the level. It helps you to have a clear view of all the cards on each level.

Note: Once you enable the toggle option to hide empty rows, the entire row gets hidden and you won’t be able to view the rows having no cards. To check the rows with no cards, you need to disable the toggle option to unhide empty rows.

Cards at the three levels are recommended to be created in the Story Mapping board as they flow from SM to Work Board. However, if you make any changes to the four fields of the cards – Name, Description, PI, Sprint in the Work Board then those changes are synched up in the Story Mapping board. Note: If the Description field is not an RTF field, then the description field will not be synced.

PI and Sprint planning

This level of the Board has PI or Sprints or both. The level 3 cards (once planned for the upcoming PI or sprints) are tagged to the respective PI and sprints at this level.

Board Activities

How to add a new card?

There are two ways to add a card on the Story Mapping board.

  1. Add a card by right-clicking
  2. Add a card using the Add Card button on the toolbar

To add a card by right-clicking, perform the following steps:

  1. Right-click the column in which you want to add a new card. From the drop-down list, select the card type.
    Note: Only those card types will be shown that you have associated with that level in the Story Mapping Configuration dialog box.
  2. Enter a name for the card.
  3. Click the Save button. The card appears on the board.
  4. To enter more details of the card, click the card. The card pop-up view opens.
  5. The top bar displays the Card type and the Card ID while the main window consists of two tabs – Details and Activity Log.
  6. In the Details tab, fill the values in the following fields –
    Title: Title is the name of the card. You can modify it anytime.
    Description: A short description of the card.
    PI: Select the PI from the drop-down list that you want the card to tag to.
    Sprint: Select the Sprint from the drop-down list that you want the card to tag to.
  7. Click the Save button.
  8. You can see all the activities performed on the card like date of modification, modified by and any description for that by clicking the Activity Log.

To add a new card using the toolbar, perform the following steps:

  1. Click the Add Card button on the toolbar.
  2. Select the Card type that you want to add to.
  3. From the Select Column to add Card pop-up window, select the cell position where you want the card to be placed.
    Note: Cells that are already occupied with a card on them are shown in dark color and cannot be selected for adding a  card.
  4. Click the Next button. The card pop-up view opens.
  5. Fill all the details of the card as mentioned above and click the Save

How to delete a card at level 1?

To delete a card, right-click the required card and select Delete. Once you delete a card from the board, it can’t be retrieved.

How to link a card to another card?

You can link a card from one level to another level on the Story Mapping board. When you link two cards at the two different levels of the board then the card at the upper level is automatically set as a Parent card and the card at the lower level is set as a Child card. For example, if you associate Card Type Theme at level 1 and Card Type Epic at level 2, then Theme and Epic cards are automatically set as parent and child cards. Similarly, when you link an Epic with a user story, then Epic is set as a parent card while the user story is set as a child card.

Note: The automatic linking of Epic and User Story is applicable only if there is one Epic in a particular column. If there are multiple epics in a column then the card at level3 (e.g. User Story) will not be linked to it automatically.

This linking can be seen with the help of WBS code. When you click the Show WBS button, then all the cards are shown with their WBS code on them showing their linking with each other.

Note: One card can have only one parent card at a time but one parent card can have multiple child cards.

  1. Linking of level 1 card with level 2 cards:

The Card Types you associate with Level 1 and Level 2 in Story Mapping Board automatically get linked with each other. So, whenever you create a level 2 card, it gets linked with the level 1 card of the same column. In case, the same column doesn’t have any card at level 1, then it is linked to the level 1 card in the left column.

  1. Linking of level 2 cards with level 3 cards:

To link a level2 card with level 3 card, perform the following steps-

  1. Right-click the level 2 card that you want to link with level 3 cards and select Link.
  2. Select Add Children. A bar appears at the bottom of the page.
  3. Select the card(s) from the level 3 that you want to link with level 2 card.
  4. Click the Save
    Note: Card at level3 can have only one parent card. Those cards which are already linked won’t be shown for new linking.

Click Reset to select a different card.

Note: The linking of cards is persisted to the Story Mapping Board only and does not get reflected in the application.

How to move a card?

Cards in level 1 can only be moved to an empty column which means all the rows starting from level 1 to level 3 of that column should be empty. The level 2 and the level 3 cards can be moved across all the columns in that level.

To move a card, select the card and drag it to the required column before dropping there.

Note: Moving a card may break the existing relationship. For example, moving a card at level 2 to another column will break the relationship with its parent card at level 1 and will re-establish a new relationship with another parent card at level 1 based on its column position.

Things to remember

While adding cards in the Story Mapping Board, you need to remember that these cards will flow to the source system, which is the Work Board, whereas all the PI and sprints will flow from the top-level Work Board to the Story Mapping Board.

Story Mapping for Multi-Board

Many a time, the success of a product or service delivery significantly depends on the right orchestration between the product management and development team. As the product management team makes a fine alignment between the organization’s portfolio objectives and churns out high-level functional goals in the form of epics and features, the development team ensures they are well executed in the smaller units like User Stories in an incremental fashion.

The whole planning and development activity can happen in a single Board or even across multiple Boards. In a multi-Board scenario, the upstreaming or grooming of epics or themes can be managed in a product-planning Board, whereas the execution of those high-level activities can be managed and monitored in the form of smaller workable parts or user stories in a development Board.

But managing the seamless synchronization among cards of different natures (themes, epics, user stories) across the various Boards can at times be difficult if we are not able to see their end-to-end mapping visually. The multi-Board feature of the Story Mapping Board helps you overcome this problem as it helps you map the end-to-end journey of the product delivery across multiple Boards in a single place only. It not only saves the time and effort of managing cards and the linking among them across multiple Boards but also keeps all the stakeholders on the same page.

For example, in the above scenario of developing a mobile app for an e-commerce website, its Themes and Epics can be defined in the Program Board while its User stories and Technical stories can be defined in the Team Board. In such a condition, you can have all the Themes, Epics and User stories across multiple Boards in one Story Mapping Board to visually map the end-to-end product journey and keep all the stakeholders aware of what is happening in the system.

Note: While using the Story Mapping Board for multiple projects, one need to ensure that the set of PI and Sprints are same across all the projects so that the cards of the Story Map board are synchronised in all the projects.

Configuring Multi-Board in Story Mapping Board

To set the multiple Boards in the Story Mapping Board, perform the following steps:

The settings for configuring the Multiple Project settings are available under the Advanced Settings in the Story Mapping Settings dialogue box.  To access it, perform the following steps –

  1. Click the Settings icon from the toolbar.
  2. Click the Roadmap Planning tab. On this tab, click the Advanced Settings tab. The Advanced Settings dialog box is displayed.
  3. In the dialog box. perform the following steps:
    1. Project – Here all the Work Boards that are connected to each other in a particular hierarchy, will by default be selected. So, if you open the Story Mapping Board from Program Level Board, then the Program Work Board, its parent Portfolio and Solution Board (if exists) and it child Team Boards will be selected here.
      Note:  This is a read-only field and no Board can be added or removed from this field.
    2. Card Type – Here you can select the card types that you want to access from multiple Boards. Those selected card types will be enabled for the Story Mapping Board.
      To select the card type:

      • Click step 2 on the left side.
      • Each Board that is selected in the Project field is displayed here.  You can select card type for each of those selected Boards.
        Note: You can select one card type from one Board only.
        For example, if you have selected Themes and Epics from Board A then you can’t select the same from Board B. Similarly if you select User Stories and Technical Stories from Board B then the same can’t be selected from Board A.
        Note: The Themes and Epics cards in Board A that will be tagged to the User Stories in Board B via the Story Mapping Board will be limited to the Story Mapping Board only. Since these Themes and Epics are not present in Board B, the user stories will be tagged to None back when seen from their respective Board. A message informing the same will also be displayed in the Activity Log for that card.
    3. Project for PI and Sprint – By default, the top-level Board from where the PI and Sprints are created, is shown here.
      Note:  This is a read-only field and no Board can be added or removed from this field.Once you have set the configuration for Multi-Board, you are now ready to perform the Board activities like Add Card, Link Card, Move Card, and others.

While updating cards in the Work board, the four fields of the cards – Name, Description, PI and Sprint also get synched up on the Story Mapping Board.  As mentioned above, the name of PI and Sprints must be same across all the projects so that the cards of the Story Map board are synchronised in all the projects.

  • Was this helpful?
  • Yes   No