PTC Windchill RV&S vs. StoriesOnBoard

PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage. Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.

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.

• Helps to advance carefully through complicated and delicate process hives.
• Improve thereby our time-to-market knowledge transfers along our portfolio.
• Enhances the performances of single step in processes as well as the processes.
• Allows for unprecedented overview in broads and in depths.

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

• It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
• The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.

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

I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system

Incentivized

PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.

Incentivized

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.

PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful

Incentivized

I wasn't involved in implementation.

Incentivized

I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.

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.

• MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency
• MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier
• In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency.
• It has also led to faster time to market for new products.

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.