StoriesOnBoard vs. TaskQue

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.

Companies that face issues due to chaos in terms of document management can really take advantage by organizing all their documents at a single place. TaskQue is inappropriate for project costing requirements in big projects.

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

• Workload management.
• Auto task management.

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

• I think Gantt charts should be here to be used as a project management tool. Moreover, affiliation with productivity tools such as time-tracking tools can make it much better.

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.

We inquired using the
TaskQue community forum and got a timely response regarding my queries. We really
appreciate it.

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.

TaskQue’s most unique
feature is the queue feature which enables you to assign tasks automatically.
We were seriously fed up with the manual assignment of tasks.

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

• High customer retention.
• Optimized project and task deliveries.