We performed a comparison between Jira, Planview AdaptiveWork, and Planview Daptiv based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so."
"For QA, the most interesting for me are boards, backlog, and filters."
"Being able to automatize the deployment of the solution has been great."
"The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components."
"The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features. Additionally, it is user-friendly."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"I like the test cases in Jira. The orange dash items view was great, and I like the features and layout of the data. It's quite different, and people are now getting their items so quickly."
"No other platform can compete on speed or search."
"Clarizen Slide Publisher has helped increase transparency and communication with project stakeholders for us."
"Clarizen's strength is reporting. Aside from reporting, I also like the ability to create customized workflow and custom actions. The workflow rules are handy. For example, you can create custom fields and dependent picklists."
"The feature that has improved our project planning the most is the ability to create custom workflows, which allows us to automate manual tasks that project managers need to perform. The collaboration feature enhances our team's productivity by allowing individuals to see the impact of their decisions on projects owned and managed by other teams."
"I like the project management solution. It's really nice."
"The powerful collaboration is definitely the most valuable and the fact that you can adjust flexibility to almost any methodology, and the easy creation of complete new functionalities without programming code."
"Changepoint gives us a view of the project status and needs very clearly, which are things that we used to miss with MS Project and Excel."
"It's difficult to pinpoint just one most valuable feature, as there are many features that can be beneficial. For the specific use case of my client's project management office, they found the project management features of the application to be particularly valuable, such as project boards, reporting, and the ability to customize views. Additionally, task management and project scheduling were also highly utilized. However, capacity planning was not used as much as the others, as there was a lack of support from executives to invest in training and implementing it due to a lack of processes in place. The project planning features, dashboard, and reporting capabilities were considered the most valuable."
"I like the reporting engine, IBM Cognos, especially the analytics. That's a good tool. It's quite strong on the ideation and capacity-planning side, which is a huge plus."
"The timekeeping features are great and very helpful."
"Users can be confused about how to use this tool as it's very complex."
"I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. It's not so good for testing."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"Not very intuitive for project admins."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example."
"The reporting needs to be improved."
"The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily."
"It could be more user-friendly. I think it is too overwhelming, initially, in terms of possibilities and so on."
"I felt like the slide publisher isn't that user-friendly. I think it wasn't that easy to use or to figure out because of formatting constraints, or maybe we need to get better at understanding some of its limitations."
"One specific area for improvement could be implementing a development environment to test workflows with live production data."
"If I start customizing too many things, Clarizen tends to get really slow in our environment and especially if I'm tunneled in an environment, like if I'm connected to my VPN."
"I find the solution has an excessive amount of features. Many aren't even kept current. Some aren't useful at all. There's an overall lack of coherence within the solution. It can make the execution difficult. Many features can easily be eliminated and it would help streamline the solution. They should get rid of 80% of the features and then really focus on the leftover 20% to make it a really great product."
"It would also be nice to see some improvements on the IBM Cognos Analytics. There's still work to be done on the analytics side of things, like your condition formality."
"This solution needs more standard connectors to other solutions."
"Expense management, simulation scenarios, and budget control could be great and useful features to include."
"The areas that should be improved in Planview Daptiv are a subject that can be viewed differently depending on who you ask. I feel they should focus on excelling in one specific area rather than providing average capabilities in many areas. For example, their project planning software is satisfactory but not as advanced as Microsoft Projects. The same goes for the capacity planning tool and reporting capabilities, which can be improved upon by using custom Excel spreadsheets or by hiring a business analyst for additional support. In short, the biggest weakness of Daptiv is that it does not excel in any one area and only provides average performance."
