Planview TaskTop Hub review
Overall Satisfaction with Planview TaskTop Hub
We use Planview TaskTop Hub to integrate AgilePlace and Azure DevOps. There are currently 18 integrations running between three segments for Epics, Features and User Stories in both Test Region and Production. It is used to manage scrum team efforts to create an end-to-end portfolio management solution between both tools. We soon will be adding Initiatives to get the full scope of work in the hierarchy. We use Planview TaskTop Hub to eliminate duplicate data entry and to automate traceability.
Pros
- Allows for one- vs bi-directional field flow which is useful per segment
- Allows for the relationship mapping of Parent/Child cards
- Allows for customization of mapped fields
Cons
- It would be great to copy collections and integrations.
- Add a search field to the already mapped fields. Example Lane/State. We have to map over 250 lanes and oftentimes must scroll to view what are already mapped.
- Ability to disassociate artifact pairs after an X amount of time.
- Version history of scripts made available within the script itself. Add time/date stamps and what changes occurred.
- We track monthly updates and each month there are typically over 30,000 updates being made which we know is saving time.
N/A - We have not used or evaluated other products similar to Planview TaskTop Hub
Do you think Planview Hub delivers good value for the price?
Yes
Are you happy with Planview Hub's feature set?
Yes
Did Planview Hub live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Planview Hub go as expected?
No
Would you buy Planview Hub again?
Yes

Comments
Please log in to join the conversation