StoriesOnBoard Reviews

Keyboard shortcuts takes the cake on why I choose StoriesOnBoard over other story mapping tools in the market. It literally saves hours at times.

I wish the ability to undo your changes was a bit more straight forward.

StoriesOnBoard allows us to map out the user journey in a visual way while also documenting the important details around implementation for our entire team to be aligned against.

Simple cards and colors work effectively. We have been able to clearly display and communicate requirements with a contractor. The story points work well for tracking our total work to be done. The contractor was able to store our initial requirement from a solution map from over a year ago, when we were finally ready to get to work, the past data was very valuable.

I don't know of anything to dislike. This seems to fill the need.

I think giving StoriesOnBoard a try is a great option. You'll find some development specific features that you wouldn't necessarily find on other kanban boards.

We've worried about keeping requirements and acceptance criteria clear and clean. This software makes doing so easy for both parties. It seems to be a great collaboration tool for building and designing software from the perspective of the contractor and the client.

Intuitive design allows for a new user to pick this up right away and use it well quickly.

Like many solutions, this has its own lexicon, and that can be a problem in understanding things until the user trips over them.

If budget is there- this can be a powerful substitute for using an actual board with stickies on it. Great in the time of Covid and the plan of more WFH

I am mapping potential products to scope out MVPs and future feature sets- then using the feature map I have made to also do competitive research and mapping.

The interface is clean and the experience straight forward. Integrations with multiple ticketing systems make it easy to manage a backlog independently from that ticketing system which makes separation of duties so much easier.

There are a few items on their roadmap that will push them past their competition:

1. User journeys: They currently do not support linking stories into journeys

2. A unique ID: Each card does not have a human readable ID that can be used for reference when the volume of cards is large.

StoriesOnBoard helps me visualize the products I work on and organize my backlog by function and priority in one view which is more relatable to my stakeholders. In addition, it allows me to separate ideas and requirements from tickets for development. That separation provides a cleaner developer experience and a more flexible requirements experience, i.e. I don't push stories to development until they're reviewed and ready which makes it clear to developers when it's ready.

In our team we use this tool to take control of the planning of our tasks, the hierarchy by points, allocation and distribution in each sprint and keep a progress report on the board. We were also able to save the board and print it.

We really don't find any dislike when we use it during a quarter. All we want to do with StoriesonBoard has a solution, even create an avatar for each team member

We find in it the perfect tool to build the product backlog, then to plan the sprints, priorize tasks, assign to team members and view the work in real time. Also we import/export the sprint backlog to other software saving time and effort

It gives an easy to use structure to capture requirements at a place.

There is no such feature that is being disliked at the moment.

What problems are you solving with the product? What benefits have you realized?

It gives an easy to use structure to capture requirements at a place.

There is no such feature that is being disliked at the moment.

Gathering business requirements and prioritizing them.

It's beautiful and easy to understand, as it's totally free and quite simple to explain even to people with a low informatic knowledge. The kanban system really improved my company working life.

The program is dispersive and kind of difficult to use as a "tool" for working management. JIRA, for example, gives the mininum necessary and is quite better in your employees working reports and reviews.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

It's beautiful and easy to understand, as it's totally free and quite simple to explain even to people with a low informatic knowledge. The kanban system really improved my company working life.

The program is dispersive and kind of difficult to use as a "tool" for working management. JIRA, for example, gives the mininum necessary and is quite better in your employees working reports and reviews.

Try to prove other kanban programs too, as they are quite useful and different. Every program has a different offer to give to your company and probably, one is better for you as one is better for another company. It depends on what you do!

It was my main program for kanban boards before using jira and it was totally useful to understand where were the areas my company needed to improve, but as the same time, it was what helped me to realize I had to do something for the organization of my working team.

It's a basic but also useful software to how to START using kanban system.

The layout is very retro, unfortunately it's difficult to manage and I found hard to put limits on tasks that were in the process of making. I don't dislike a "straight to the facts" attitude, but at the same time I have troubles managing something that unfortunately looks like coming out of a former Windows operative system.

As written above, I would like a different layout and other form of visualization, as it's actually not that good and difficult to read sometimes (it's small font a choice?) let your users decide how to use your software.

It's too disorganized: unfortunately there are WAY better products to utilize a kanban organization of work.