Microsoft Project vs Planview Daptiv comparison

"The tool has a simple and excellent approach."

"It is very stable. I haven't had any kind of issues with it. It is also very scalable."

"Microsoft Project offers comprehensive project overviews and the ability to rate down what we have and what we need in terms of software."

"The resource allocation features, which help allocate resources to tasks, are quite valuable."

"Microsoft Project integrates well with the Microsoft Office family of applications. It has plugins that interact with it and you can use it with Microsoft Teams. We can use plugins to communicate with JIRA, Projectplace, and Planview. It's not widely used in the company, of course, but it's something that can interact with the official tools that we have."

"The most valuable feature of Microsoft Project is status reporting."

"We value all the features. Previously, we used Jenkins for similar purposes, but Microsoft Projects works fine. We're looking to improve integration with different clusters on production and automate various aspects of software development. This includes integration for alerting, monitoring, and pricing purposes, among other things."

"The integration between SharePoint and Power BI has been great."

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

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

"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 should be easier to break things. Breaking up the visualization from the task is sometimes a little bit tricky to do. You can do it, but it takes a minute. It's not an easy function to do. The way you have to format it and stuff like that takes a minute."

"The collaboration has room for improvement."

"When a project plan becomes huge, it is painful to arrange and structure the project in Microsoft Project. Currently, you require a separate product for managing agile projects, and people are using Jira and Rally to manage stories in agile. Primarily, on the software development side, people are kind of moving away from Microsoft Project."

"They should assist with tedious tasks."

"The online version of Microsoft Project lacks some functionality compared to the on-premises version."

"Project is not easy to scale. It isn't a cloud-based solution where everybody can utilize it at the same time without version issues when you save your file. We use it at the enterprise level, but you have to share the files to others within your organization through Teams or SharePoint. One improvement would be to transition to cloud-based functionality. However, that might limit the functionality in other ways."

"The Gantt set needs to be improved. The grid lines needs to be more interactive."

"It is a traditional Waterfall-based solution, so it doesn't lend itself particularly well to Agile development. You can record Agile sprints within it, but it is not really an Agile-based product. It can store the basic information about budgets that an Agile set of work is looking to use, but that's about it."

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

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

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

"Expense management, simulation scenarios, and budget control could be great and useful features to include."

"The product is not expensive. My company has opted for an annual subscription."

"I am not aware of any additional costs apart from the standard licensing fees of the solution."

"We have to pay for a yearly license for Microsoft Project."

"I believe the licensing for the solution is based on an annual fee."

"The cost for an on-premises-based license is a one-time fee, and the cloud-based is an annual payment plan."

"I am not involved with this."

"We purchase perpetual licenses due to the high cost of subscriptions, which are about 1,000 Australian dollars."

"The license is a one-time payment but it is expensive."

"It's a yearly license, but it's not an open license. It's based on users and their roles. So your administrator is priced differently from your timesheet user."

"The licensing is pretty complex. Each kind of user is a different price. It's approximately $300 per year. They charge additional fees for technical support and other additional services."