Orangescrum vs. StoriesOnBoard

This is a good thing for medium/large companies for inside the company and/or for interacting with remote employees/freelancers. As the program facilitates the interaction between employees and managers it speeds up the distribution of tasks and allows managers to identify possible problems on the fly. For indie developers - it's a little expensive.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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.

• We tested the free version of the program. It improved communication within the team.
• Allowed to trace performance and time spent on tasks. Each team member was aware of the status of the tasks and could plan their work.
• Simplified interaction with managers, as it could present the results in the form of Gantt charts.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

• The program interface is overloaded. Especially when there is little time for a detailed description of the tasks.
• I would like a faster way to publish the result at the completion of the task.
• Projects and tasks are two different workspaces/pages. Personally, it would be more convenient to combine these things.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Trello was excellent, but we did not choose it because of the price and relatively positive feedback from employees using Orangescrum who wanted the easiest and fastest way to create reports so as not to be distracted from work (as a two-click report).

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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.

• It accelerated the work of the team, but the mastering of the program interface was slow.
• The interface is not intuitive. It proved to be quite complicated.
• For managers, the program has facilitated reporting and streamlined team tracking.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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