IBM IMS vs. StoriesOnBoard

We have built a database of a network of bank branches with all the needs of security and recovery/restart. It requires knowledge of obsolete maintenance languages and perhaps it is too rigid in the schemes.

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.

• Security
• Reliability
• Big volume of data and good performance

Incentivized

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

• Certainly, not being a DB relational penalizes its use
• It should be more flexible
• Open up to more recent languages

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.

Essentially, for a question of reliability and scalability, the performance has always been of an enterprise level. The utilities are efficient and effective.

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.

• The investment made about 20 years ago that has been fully repaid
• Reliability and security of investments
• Unfortunately, it is quite outdated and therefore maintenance costs are higher because the skills are not always available.

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.