Asana vs Planview Daptiv comparison

"It is stable and easy to set up."

"The solution's user interface is very good."

"I love the way it monitors all of the current and past projects, and it sends notifications to keep everything on the track."

"The most valuable feature of Asana is the tracking of comments and documents in one place."

"The only thing I love about the product is that it is beautiful."

"The ability to build subtasks and break things down off of our major tasks has been very valuable. It is very stable and extremely scalable. The initial setup is very simple."

"It is very good for managing the timeline. I'm a quality manager, and I have different testing projects running with different work breakdown structures. Asana makes it very easy to implement and monitor the plans. It is easy to move the tasks and complete them, break them down, and assign them to people."

"The time we are investing through departments with Asana is valuable because we are receiving requests or updates for projects without investing time in meetings or writing emails."

"The timekeeping features are great and very helpful."

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

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

"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 would be beneficial if Asana had a predecessor feature that automatically adjusts all subsequent dates when changes are made to a timeline. For example, if I assign a designer four hours for one task and two days for another, and the completion of a task takes longer than anticipated, it would be convenient if updating one date could prompt the adjustment of all other relevant dates. Essentially, this feature would streamline the process and eliminate the need for manual adjustments."

"The messaging feature could be better."

"The main dashboard, where there is a list, needs improvement."

"On the development side for technical project management, Asana is missing features. We only use it for discussing tasks and strategies, and we use it for customer to-do lists. It doesn't have the source code integration that Jira and Jira Service Desk both have."

"In Asana, there's no way to add a custom date field."

"Auto-shift is an essential feature for planning, but it's currently not there. It should have this feature so that when you move a task that depends on another task, the dates should be auto-shifted. For example, you have two tasks dependent on each other. When the parent task is moved or delayed, the child task should also be delayed, and the date should be shifted. When we have a very long timeline, it's very complex to go task by task and shift the dates on the task. Auto-shift is a fantastic and basic feature of project management, and having such a feature in Asana would make our lives much easier. If Asana added this feature, it would complete the suit and close the project management cycle because currently, there is a gap."

"In some instances, there were subtasks where more than one person needed to review it, but I could only assign it to one person. I would have to create a subtask under a subtask and then assign it to other people. This could be improved."

"We don't get enough notifications."

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

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

"This solution needs more standard connectors to other solutions."

"This solution is reasonably priced."

"Asana has two different types of structures: company vs workspace. Company is really best if all the users you plan to assign work to are all internal (have the same corporate domain in their user ID email address). Once one person signs up (even for a free account) with a corporate email address, Asana will automatically relate that person to that company, if it already exists. If you plan to use it for external collaboration as well as internal, then creating a workspace is a better approach."

"We're on the business tier, which is $25 a month if you're on an annual contract. It's $31 if you're on a month-to-month contract. In my experience, there are no hidden costs with Asana. I know Smartsheet has these add-ons that you can buy, which is an additional cost, but Asana doesn't have any add-ons that I know of. When you're trying to scale the product and want to add users, you have to do it in buckets of five. This is also something to consider."

"The cost is $25 US per unit per month."

"We paid a monthly licensing fee for the product."

"There is a free version of Asana, but we use the paid version to receive all the features we want. The overall price is reasonable."

"The price of the solution is reasonable."

"The solution's free version can be used for basic functions."

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