Congratulations! You have installed Easy Agile User Story Maps for Jira.
So, where to from here? How do we create and manage User Story Maps?
Here's what we'll cover in this article:
How do I view my Scrum and Kanban boards as Story Maps in Jira?
Once installed, each Scrum and Kanban board in Jira can be viewed as a Story Map. To access the Story Map, click the 'User Story Map' button above the backlog icon on your Agile board.
Please not: Jira 6.4 and 6.3 include the ability to turn Project Navigation on or off. Jira instances with Project Navigation tunred off can access the Story Map by:
What if there are no epics in my backlog?
When there are no epics in the backlog a welcome screen will be displayes with a video included, providing users with an overview of the concepts of story mapping in Jira.
Creating Epics (Creating the Backbone)
Across the top of the board you will create a horizontal row of epics. Each epic represents an activity of the users flow through the product, This is often referred to as the 'backbone' of the Story Map.
For Example: a fictitious job applicant tracking system may have several activities from Requisition through to Onboarding - there will be an epic for each of the activities right through
These epics can be dragged and dropped and the order of the epics will be reflected on the backlog using Jira ranking.
Creating User Stories (Flesh on the Backbone)
From the backbone of epics we add User Stories to support each activity. These are ordered by rank below each topic. For example:
To create a new story associated with an epic, click the '+ Create Story' button under each epic. This will bring up the condensed create issue dialogue which automatically adds the association.
The stories within each epic can be reordered. This allows the team to order the stories in terms of importance or value to the user.
To reorder a story within an epic simply drag and drop it into place. You will see a grey drop zone to guide the placement.
A key aspect to story mapping sessions is sequencing work into upcoming sprints or versions, for example:
By switching the view to 'by Sprints' or 'by Versions' you can drag and drop issues between sprints or versions.
Versions are ordered by their Release Date.
Quick Tip: some teams pick an arbituary date, like the first of the month to show their intent to release a new version in a given month.
As you drag and drop issues betwen sprints or versions, the estimate statistics will be immediately updated, helping teams effectively plan upcoming sprints.
Below you can see 'To Do' work (Blue), 'In Progress' work (Yellow) and 'Done' work (Green).
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs