“I hate making JIRA cards so being able to push and sync the work I do in StoriesOnBoard to JIRA is a major time/sanity saver.”
Eric Avarell - product manager
Lightweight solution for high level planning
Time-saving story writing features for product design
Use the brainstorming mode to involve team members
Enjoy the real-time updated two-way synchronization
Prioritize backlog items effortlessly
Boost visuality by custom labels and tags
Trusted by these companies and many more
"I love how easy it is to build out and arrange/rearrange a story map. The navigation features are very easy to pick up or intuit."
James Childs - Scrum Master
Three-level user story mapping for an effective product design.
Fast story writing features let you collect user stories tremendously easy.
Add unlimited details, attachments or comments to user stories.
Use the intuitive brainstorming mode to get all valuable ideas.
Viewers can join to the workspace in real-time and can leave comments for free.
User story maps are visual aid for non-technical stakeholders.
Boost visuality and team's engagement with user personas.
Create compelling BIO, add details for a better understanding.
Assign personas to epics and visualize user journeys.
"Two way sync makes it an easy choice no matter what engineering or development team prefers."
Daniel Swid - Agile Engeneering & Customer Innovation
Integrate the user story map to JIRA project with just a few clicks.
The levels on the story map will be synchronized to epics and user stories.
Create versions on the story map, they are synchronized too.
Descriptions and story points are mirrored and updated.
Create easy-to-understand specifications.
Track current iteration with real-time updated user story status.
It's super-easy to insert new stories in the middle of the backlog.
Drag tasks between epics or releases with one movement.
Always with you! Use it to present the project's status.
“StoriesOnBoard filled a gap between the planning meetings and the day to day project execution.”
Planning versions is tremendously easy by arranging user stories with drag&drop.
Sync version structure and version details to JIRA project.
Ongoing project? Import JIRA backlog with just a few clicks.
Schedule versions smoothly, arrange them by drag&drop.
Don't let the dev team's board overloaded, push user stories to JIRA version by version
Preview what the next month or quarter look like
Daily Tips, Story Map Examples
25 Tips For Better Story Mapping
Product Discovery Cheat Sheet
Build Software that matters in 9 steps
No Credit Card Required
You'll easily find plenty of valuable education materials on the net, but let me summarize the story mapping method in 5 short steps. First off, user story mapping is a visual product planning method, that is originally designed for white boards or office walls. It is very intuitive so it's easy to learn for non-technical participants – and involving them delivers additional value to a design process. Thanks to online tools, the process moved to virtual white boards and can be integrated to a JIRA project.
User story mapping expends a lot of effort focusing on the end user, so you need to frame the problem and the users' goal(s). What are the main requirements that need to be satisfied using the product? Let's write down these goals in a narrative flow, if it's possible. For example, you're designing an online accommodation platform, where visitors can find, compare offers and book a room. Our user would find hotels, then she/he would choose one and book a room.
For better understanding the user map journey, what steps does a user take to reach the goal? The basic journey to find hotels could be the following: visit main page -» start a search -» refine results by adding filters (e.g: period) -» rearrange search results (e.g: by price). Collect all steps for each goal. The easiest way to discover the whole journey is following the narrative flow.
Now we have the product backbone, let's find out how to solve some steps. You don't need to think in features, just write down the user stories – e.g. “as a visitor I'd like to land on a clear, easy-to-understand website”. Try to write short/smart user stories from ideas, e.g. “basic landing page” or “responsive website”, etc.
All the online story mapping tools offer a description section, so you can add notes and useful thoughts to a card. Moreover it can be used when specifying user stories or tasks. If you didn't involve a brainstorming team previously, now you should definitely do so. Remember, the more participants, the more ideas. To keep the brainstorming team focused, you can restrict ideation to a single goal or step.
You didn't need to concentrate on priority in the previous step. Now you should evaluate user stories which deliver more value or which are easy to develop. Of course, you can use your own prioritization method, or discuss it with the stakeholders. Express priority order on the story map, and place high priority cards above others. Continuing with our example: “basic landing page” ranked higher than “responsive landing page” and “highlighting promotions” has the lowest priority.
Prioritization gave you some guidance on where to start, but it's just a half-baked solution to schedule a dev process. You need to slice the backlog horizontally into versions. Frame the Minimum Viable Product by moving cards into the first version. Check completeness by retelling the narrative flow with the user stories. For example: user enters the basic landing page -» search hotels by name -» filter offers by date -» rearrange results by price, etc... Can the user reach their goal? If the answer is yes, you don't need to add more items to the first release. The next step is to group user stories around working features and schedule the subsequent versions.
As I mentioned previously, doing the story mapping online provides robust opportunities to integrate your story map to Jira. Top-level cards can be synced as epics, and user stories remain the same in Jira after setting up the integration. According to the backlog size or the product need you can link goals to epics in mid-size projects and sync steps with epics in larger projects. In addition you can send the backlog release by release, so you can keep the JIRA project clean. Then you can break user stories into tasks in the issue tracker tool.
Share project with your customers by invititing to the story map. Customers get a intuitive view of the project and they can leave comments.
Introducing the brand new JIRA structure sync feature is a perfect occasion, to sum up, all the benefits of using the integration. Whether you have an integrated backlog or not, planning in JIRA is annoying, and poor planning leads to a failed product. So planning on a visual backlog is vital for a product owner.
Product discovery with JIRA can be annoying, because of lack of discovery features. If you miss the product discovery phase, you’re risking a failed product. Follow us to learn how to integrate a visual solution for product discovery to the JIRA project. At the end of the article you’ll get a guide for an effective product design.
Product owners often struggle with involving executives in product development. Convincing a decision maker about additional staff or budget can be hard when he/she doesn’t really understand the project. In addition, non-technical stakeholders don’t have a high-level view of the project. Poor communication and a lack of shared understanding lead to a failed project.
In spite of having to pay for all users in JIRA, you don't need to pay for the whole team in StoriesOnBoard. Team members can join as “editor” or as “viewer” to StoriesOnBoard. The monthly or annual fee is calculated upon the numbers of editors. Viewers can join without registration and for free. Moreover they can comment on backlog items (after a simple sign-up process).
Editors can build and manage user story maps, on different permission levels. You can customize permissions individually on each workspace and different story map. Viewers can join the project for free, open a story map and read the item details. In addition, they can leave valuable comments on cards after signing up for StoriesOnBoard.
Hierarchy sync means that two levels of the story map can be synced to the JIRA project. You can choose top-level or second-level cards to synchronize as epics, and you can send user stories as user stories to JIRA. It works the same way when you import items from JIRA. The epics will appear on the selected level (top level or second level) and the related user stories under them.
Hierarchy sync is optional, you can import a JIRA project without structure sync. Choosing this option, you can import tasks and bugs, too. After importing all the items, you have the opportunity to arrange cards according to your business needs.
Card detail/description is synced with all the text formatting. Status and estimations are also synced and updated in real-time. You can add a direct link to each backlog item to jump back to the story map with one click.
StoriesOnBoard boosts the dev process when you start building a product from scratch, and it's also very useful when importing a running project to the story map. For example, you can discover holes in the user journey, or missing features, etc. In addition, using structure sync helps keep backlog items in the original place.