A tool to feel good

Overall Satisfaction with StoriesOnBoard

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.
  • 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).
  • 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).
  • (Negative) There were discussions about the type of Activities, Steps, and Stories (independent of the tool)
  • (Positive) All received a clear status about the MVP and the road map.
Miro: The handling in Miro was not comfortable enough.
Easy Agile User Story Maps for Jira: The integration with Jira was a great idea, but the handling on the map was not good. Also, there were only 2 layers, which made it very difficult to define the cards.

Do you think StoriesOnBoard delivers good value for the price?

Yes

Are you happy with StoriesOnBoard's feature set?

Yes

Did StoriesOnBoard live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of StoriesOnBoard go as expected?

Yes

Would you buy StoriesOnBoard again?

Yes

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.