Planview AdaptiveWork vs. StoriesOnBoard

I've been an AdaptiveWork (Clarizen) admin for the past 14 years, so I've seen much improvement since I started working with the product. I'm very happy we can utilize the hybrid mode by using the cards, I think this was long overdue but it works very well.

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.

• Many ways to acclimate to the system; documentation, videos, community, and contacts.
• Planview provides scalable customization options tailored to the unique needs of each business unit or department. Easily add or remove fields in the system. As the admin, it was easy to learn how to configure.
• Offers flexibility to adapt to existing systems and align with organizational workflows and processes. There are multiple ways to customize each part of the system to meet our needs.

Incentivized

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

• When it comes to reports, it would be great if there was an easy way to roll-up the results instead of having to create configurations to summarize data.
• The consultant experience has not been great when it comes to more advanced needs for configurations. The consultants are in a different timezone which limits hours to work together and it seems hours are spent trying to determine what the requirement is and when the initial thought is that the configuration is possible, it may result in not being able to assist.
• Charts in the reports section are not able to be exported
• When pulling a report together, you need to make sure you pull from the right "item" or level. If you decide you need data that resides in another "item" or level, you need to re-do the report from the beginning.
• Because the system is so configurable and I imagine different clients use the system differently, when you need something automated in your account, where you need to pull a consultant or SME in, the person doesn't necessarily understand your configurations and how things work so they are unable to give recommendations on how to solve problems that don't impact other configurations you already have set up in the system.
• Templates cannot be updated unless they are pulled into a project and then re-saved. In the templates module, you are not able to open a template and edit to re-save. Therefore, making updates to a template can be very time consuming having to find a project to use to pull it in, make updates, re-save and then pull out. It would be great if the templates module allowed you to edit the templates and re-save.

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 give my renewal of this product a 9. It's only because we never know what product may come out next and how other factors in our office political environment may cause impact upon this. If I always had my way, this is what we'd settle on as our de facto project management system.

It is easy to configure, intuitive. The customization process is in some ways better than Salesforce.com. It has a great UI. It does however depend on how it's implemented.

The design of it is generally fine, however the ability to data upload people from a spreadsheet is an obvious miss.

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.

Sometimes it is slow when everyone is entering their time on Fridays or Mondays but other than that we rarely see downtime and maintenance notifications are well in advance.

Reports: Quick to Reasonable

Most Ancillary Pages: Quick to Reasonable
(By "ancillary" I mean lesser used/master data maintenance pages - e.g. People, Customers, Individual Tasks, Milestones, etc.)

Work Plan (with 100 sub items): Reasonable to Slow

It's a good experience overall. Clarizen was useful when needed. It's mostly needed for advice on how to do more sophisticated actions or how to change something that was set up administratively. It's seldom used otherwise. The product consistently works, the documentation is acceptable, and the generally intuitive product is easy enough for most staff to pick up without much issue.

Incentivized

• We worked with a Project Manager on their side. He was very good about developing a project plan to hit our goal. I think we had weekly or twice weekly calls – very steady cadence over 3 month period.
• Their PM skills were great – kept us on task. For the last week, they sent 2 people on site and they did training for power users. After that a couple of them revisited here

Our trainer, Alex, is exceptional and knows the product really well. I swear he must have wrote the product himself! His manner with training is very easy going, gives you homework that is applicable to what you need to learn and stages it correctly for you. It was a pleasure to be trained by him.

I performed the implementation with our Clarizen provide trainer, who knew the product 100% and it went quickly and without a problem. It was a pleasurable process without the problems other software implementation often encounter. Kudos to the Clarizen team for making this a worry free process for their clients because it is worry free.

Planview AdaptiveWork was the right size, at the right price point that fit our customization and integration flexibility. It is intuitive to use but allowed us to add complexity as our needs grew

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.

• By implementing Planview AdaptiveWork on a company-wide level, we have been able to remove the other project management tools we have been using and consolidate our costs for technology down to a single tool
• The ability to incorporate cross-departmental work and communication has streamlined our project management processes to a point where we can work seamlessly together without interruption trying to consider the gaps between tools
• Reporting capabilities from the unified tool has given our leadership insight and the ability to make strategic business decisions more effectively than ever

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.