StoriesOnBoard

Score1.1 out of 10

8 Reviews and Ratings

Community insights

TrustRadius Insights for StoriesOnBoard are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Business Problems Solved

Users have found the product to be extremely helpful in prioritizing upcoming build phases and maintaining sanity throughout the process. They appreciate the ability to import stories directly into Jira or other project management platforms, allowing for seamless work. The software has also been praised for its ability to keep requirements and acceptance criteria clear and clean, facilitating collaboration between contractors and clients. In addition, users find it highly useful for early project planning and throughout the life of a project, as it provides a high-level view for work implementation and helps with team alignment, quality delivery, and project status tracking.

The software is not only used by software development teams but also by student teams to better understand products and solutions before diving into coding. Despite being an essential tool for agile story mapping workshops with stakeholders, some users have switched to other platforms that integrate story maps with their workflow processes. While reviewers consider it the best storyboarding tool in the market, they do mention areas for improvement such as the lack of real-time collaboration and a clunky interface. However, even employees unfamiliar with the user story process find it easy to use and intuitive. The customer support provided has been excellent according to reviewers, who have introduced this tool to others and have been using it for several years.

Reviews

3 Reviews

Great tool to keep external teammates in the loop

Rating: 10 out of 10

February 24, 2021

Use Cases and Deployment Scope

My team uses StoriesOnBoard to facilitate communication among internal and external colleagues. Since some functions of development are outsourced, we needed a tool that supported shared understanding. It is also a challenge and rather a lengthy process for a new external colleague to pick up on processes. We find that user story maps can help with that.

Pros

User role management
Jira integration
Keyboard shortcuts
Filtering by personas

Cons

Integration for NextGen projects

Likelihood to Recommend

It's a great end-to-end tool from ideation through prototyping to maintenance. The Jira integration makes backlog management efforless for Jira users.

Verified User

Analyst in Information Technology (1001-5000 employees)

Vetted Review

2 years of experience

A tool to feel good

Rating: 10 out of 10

February 22, 2021

Use Cases and Deployment Scope

After the company was founded, the software was developed without any feedback from the users. This led to the fact that often only features were implemented and bugs were neglected. There were also many features developed that were not used by the current users. After a reorientation, StoriesOnBoard is very helpful in defining a new, clear MVP and determining the further road map. We also use the tool to illustrate other processes, such as a customer journey and an employee journey. As a startup, everyone who works directly with the software and has gained experience in the exchange with customers is involved in the user stories: CEO, Support, QA and Engineers.

Pros

Individualization of maps, annotations and colors.
Clear display depending on the situation (hiding stories).
Handling of the cards in case of changes.
The possibility to change content directly in the overview (title, annotation, color).

Cons

Switching the view to a vertical mode (easier to scroll).
Better availability of information on user story mapping.
Possibility to link to activities and steps from other maps (Context).

Likelihood to Recommend

As mentioned earlier, we also use StoriesOnBoard to create other processes (customer and employee journey). We use the swim lanes to differentiate between measures, tools and processes and working with them is very easy and understandable for this purpose.

Less easy is the use of context, i.e. when one part of a story map depends on another story map. This cannot be avoided (at least for us) to avoid creating redundancy (and the risk of creating different stages). At appropriate places, we refer to the other map in the title.

Jennifer Schenkenberger

Support Engineer in Customer Service at Pxio GmbH (11-50 employees)

Vetted Review

We love StoriesOnBoard!

Rating: 10 out of 10

February 21, 2021

Use Cases and Deployment Scope

We use Stories on Board to create story maps for upcoming software (SAAS) development projects. We start with a smaller group meeting, engineering and business leads, map out the high-level "happy path flow", and then add details on sub-cards. After getting a shared understanding and agreement on that, we use the story map to socialize with a broader set of stakeholders, updating with their feedback as we go. While the story map is a living document, we generally will take a screenshot of it and include it in our technical solution documentation and business documentation on our document management system, Confluence. We find StoriesOnBoard to be extremely user-friendly and easy to use, adding cards and sub-cards, adding details on cards as needed, and with the ability to collapse the view to hide the detail cards. While a user experience is almost never linear, we use the "happy path" to map out as best as possible a linear flow.

Pros

Easy to add, remove, and move cards that represent different parts of the user experience (either external or internal users).
Flexible with different views, zooming in, zooming out, hiding detail cards, etc.
Can add an infinite number of viewers without having to pay more.

Cons

It's perfect for our use case, I don't have any real complaints!

Likelihood to Recommend

Wells Blanchard

Senior Technical Product Manager in Product Management at McGraw Hill (501-1000 employees)

Vetted Review

3 years of experience

View profile

Loading Reviews List....