We performed a comparison between Broadcom Clarity , Jira, and Planview Daptiv based on real PeerSpot user reviews.
Find out what your peers are saying about monday.com, Broadcom, ServiceNow and others in Project Portfolio Management."The ability to have all of the data in one place from risks and issues to resource capacity and actual utilization."
"Broadcom Clarity PPM's most valuable feature is the plenty of modules, such as portfolio, project, resource, and time."
"I appreciate the report that shows how utilized a person is set to be within the coming months. I use that feature a good bit."
"The new UI makes it easier for people to go in there and know what to do. To train people, it's faster, more intuitive."
"Project Management features that are excellent in managing the Project Management Life-cycle, along with other related details like Financials, Resources and flexibility to customize, as per requirement."
"It has highlighted areas in our company that were deficient in resources. It has allowed us to hire, then realize more benefits regarding the number of projects we can get done."
"Absolutely, the most active community I have ever been on."
"Having information all together in one single source."
"A very comprehensive product; easy to set up and is very user-friendly."
"It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want."
"I like it for team collaboration and task management. I also like its analytics and dashboards."
"This is a user friendly solution."
"The burndown charts help track projects."
"JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for."
"We integrate Jira with QRadar which is helpful."
"What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best in class solutions, but it's so well integrated. You will not have many problems with integration."
"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."
"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."
"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."
"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."
"I think there's still a little bit of opportunity that we can do some stuff better in relation to the financial part of it; just that easier integration, that look and feel. Our project managers, and obviously finance people, love to interface and use of Excel. The more we can get CA PPM to behave in a similar way, which we're already starting to gain in that path, will be absolutely fantastic."
"We're looking at adding the Agile piece to it. I want to make sure that that integration is very smooth."
"The solution could improve the way the workflow is developed. I think they could be more dynamic because they are in a way static. They're very powerful, but they don't have any interaction with end-users."
"The look and the feel of 14.4 is a bit antiquated."
"One of the areas that we would improve upon is not necessarily with the tool, but having more tips/tricks on adoption. How to get people outside of the PMO to use the tool and get the information."
"CA Communities need a lot of improvement."
"Broadcom Clarity PPM should improve how the reports are being generated and contracts management."
"In the timesheet UX, you can't do things like splitting time, managing overtime versus regular time, very easily. That would be helpful."
"We'd like to see more collaboration tools implemented within the product itself."
"A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product."
"Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."
"I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice."
"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."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"Expense management, simulation scenarios, and budget control could be great and useful features to include."
"This solution needs more standard connectors to other solutions."
"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."
"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."
"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."
