We have an important update about JIRA Integration which will affect your workflow and connection.
You should take action now to re-enable your connection to JIRA.
Earlier in the year Atlassian announced an upcoming change in the way usernames work in JIRA and third party applications. Today 17/4/2019 the support for usernames was removed and now requires a API Token to connect to your FeatureMap.
From today FeatureMap will NOT connect to JIRA using the old username and password. This will disable automatic sync and a new Token will need to be generated to continue using JIRA integration.
The new API tokens offer more security and can be revoked at anytime. An active token is required for synchronization.
Generate your new API token:
To create an API token from your Atlassian account:
User Story Mapping is normally a technique for Product Development, but you need not limit yourself for just one task or function.
Here we explore outside the box and look at applying User Story Mapping to product lessons, customer feedback, marketing strategies and even Christmas lists.
User Story Mapping is most commonly used for software development. You are able to outline and see the bigger picture of your product. You can prioritise the user stories, identify the journey of your users and involve all team members to have a shared understanding.
It is not just a tool that you use to outline the project, it is a technique applied to every step of the way. You can change, adapt, reprioritise, add further tasks, scrap old tasks, and so on. While ideal to sit on a wall in the office with post-it notes one large company has a large 75″ display in the office with their FeatureMap on display for all offices and departments.
Moving to the digital has its benefits and allows all departments and those remote to the office to collaborate. In addition, you can allow your shareholders and in some cases, even your customers to get involved.
Occasionally after a campaign, season, or annual review you look back at your product and hold a session of “product lessons learnt”:
Promote the recurrence of desirable outcomes
Preclude the recurrence of undesirable outcomes
Using User Story Mapping here can help you outline the user journey. Define each step which worked, and highlight what should be removed or revised.
Using layers you are able to prioritise your learnings by the impact on the user using analytics data, internal comments and observations, incident reports, and any further data or knowledge that can build a picture about your product and its presence.
Your goal is not to create a product but to highlight the users experience to learn.
Developing your map can involve the customer, allowing a public-facing map and open process you can get feedback direct from the customer.
Taking suggestions, feedback and ideas from customers is the golden goose.
We’ve all had the occasional user when you open up your ticket support system or email and in the inbox sits 10 emails all from the same person hammering feedback after feedback. These users are my favourite, and while initially a shock to the system, they offer the best value.
Taking all feedback to build your User Story Map and highlight the pain points reported.
Set columns for feedback, suggestions, bug reports and crashes.
Again, do not set this as a product development map but a feedback map and this can help you prioritise your next steps for development and also feed directly into Product Lessons.
Marketing and email strategy
When defining the user flow from a cold lead to a warm lead, add in tracking, and stages you’ll soon hit a complicated process. User Story Mapping, the super-hero of project management is here again.
Setting our a User Flow from cold lead, to warm lead, to sign-up, to conversion can all be done with a FeatureMap.
While mailing systems, like mail-chimp, can work exceptionally defining a campaign, following a user along a sales process (especially when plugged into marketing) is broader than MailChimp.
Happy Holidays to you all, and time for a bit of fun, but an entirely function one.
This year I was planning out what to buy my friends, family and fellow office workers and wanted a way to track what I had purchased. In some cases, I have commissioned artwork and needed picture frames and had presents that became a multi-stage process. I turned to User Story Mapping and whipped up a FeatureMap to help manage who was getting what!
We started this intro to story mapping with a basic run down and a simple exercise taking you through the morning tasks and making a map. Now we will look at how to define features in a product.
When you first start off it is best to have an idea of the ideal product, but have not yet started on your product roadmap. Instead start with the user’s normal workflow (minus the app or software) and figure out how to translate that flow into a product experience.
Below I have outlined an example case study of arranging a conference with the persona of the organiser and board member.
The team sat down and exchanged tasks, goals and ideas. We then started to construct a story map based on the conference organiser’s first set of responsbilities and workflow.
After the initial workflow you will notice the goal at the top linked to the persona.
The main activities are in the first row, divided into further tasks in each column which details each activity.
On a card we have further detail such as:
After we established the conference organiser’s tasks we then expanded the story map to include the expanded responsibilities and workflow of the entire Team.
With this map now completed we can see the user workflow and what features we need defined.
When building your story map, you should include all the relevent people, regardless of position, in the team. Due to their different foundations and interests, they all get valuable points of view. Everybody has an unmistakable and common comprehension of what they are about to build together.
Product owner, testers, technical lead, customer support, architect, UX/UI designer, sales and marketing, etc. All have their own techniques and requirements which will help you create your map.
How to build a story map
If you are brand new to user story mapping, we have a short and sweet exercise. Let’s take a simple real-life example of “getting ready for work”.
Start with the goal.
What is the story map about?
What are you trying to accomplish?
The main overall purpose.
Second list your main stories, your main tasks or activities. From left to right, insert the main steps of the story map that need to happen.
Move on and detail each main list – column by column, left to right.
In the case of product features, the layers can be then developed and you can plan out MVP‘s, or product iterations with each following layer.
When exploring product features, build story maps for multiple options that solve the underlying problem. Allow your entire team to contribute and come to and understanding of the final decision.
Story User Maps are ideal for allowing a team to design out a product feature and reduce the need to go back half way through development because XYZ requirement was missed out.