Jira Product Discovery vs. StoriesOnBoard

It was great for handing off projects to Developers and give it into their hands especially by being able to connect to Product Board. Was tricky though sometimes going back and finding things when those backlogs get really lengthy and titles start not helping as much...etc.

Incentivized

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.

• Tagging
• Searchability
• Sprints

Incentivized

• User role management
• Jira integration
• Keyboard shortcuts
• Filtering by personas

• can get overwhelming with lines of data, maybe clean it up and split things more clearly?
• Lots of white on white and the UX can be kinda tricky to navigate
• Can almost have too many different ways to tag things where it can get really confusing, Simplifying might go a long way.

Incentivized

• 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).

StoriesOnBoard works really well; all features are well thought through. It could look a bit fresher, although the new updated dashboard is already much better than it was.

productboard is my favorite, but that one is more Product oriented where Atlassian Jira Product Discovery seems more Dev focused so it is nice those tools compare. Azure is really nice in the UX and the way it presents the sprints and the stories in an easy manner. Atlassian Jira Product Discovery is great when creating the stories within itself and also works with productboard better than azure does currently.

Incentivized

The only other competitor we looked at was cardboardit.com. Both had solid functionality, but StoriesOnBoard was more user-friendly and quick to learn and use in our opinion.

• Has helped us improve our tool
• Has been a bit confusing at times causing rework when unable to find original ticket
• Has been useful in communicating product needs to development

Incentivized

• StoriesOnBoard (and story mapping in general) creates a low-cost visual method of aligning on high-level business and technical requirements early in a project and provides an ongoing reference as the project progresses. Having this alignment is critical for the later stages of the project.