AgilePlace is a project management solution built around flexibility, data-driven analytics, and workflow automation. The software was acquired by Planview in December 2017 to expand that company's capabilities.
$19
per user, per month
Planview Hub
Score 8.4 out of 10
N/A
Planview Hub provides scalable, sophisticated near real-time integrations to help IT leaders and their teams eliminate inefficiencies.
N/A
Pricing
Planview AgilePlace
Planview Hub
Editions & Modules
Teams
$19
per user, per month
Scaled Teams
$29
per user, per month
Custom
Contact Sales for Quote
per user, per month
No answers on this topic
Offerings
Pricing Offerings
Planview AgilePlace
Planview Hub
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
All editions include unlimited boards.
—
More Pricing Information
Community Pulse
Planview AgilePlace
Planview Hub
Considered Both Products
Planview AgilePlace
Verified User
Anonymous
Chose Planview AgilePlace
AgilePlace is better than JIRA when it comes to ease of use and intuitiveness of the tool. Card based model and ability to customize/tailor the way you want makes AgilePlace is a great tool. Look and feel as well as colored cards, makes the board layout much more easier to …
All these tools are different and have different uses. Depending upon SDLC your organization uses, you would use any of these tools. They all have their plusses and minuses.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration.
Front-End Web Developer, Office of Mediated Education
Chose Planview AgilePlace
I use Trello a bit for personal use. It's much less powerful than LeanKit, but it's also a better design and simpler to use. ServiceNow has some kanban board stuff built-in, but I wasn't super impressed with it. JIRA seemed to be even more complex than LeanKit for the short …
I think that LeanKit is very similar to Asana's Kanban feature and Trello, but is much less sleek looking than Asana. Asana's clean and sleek UI makes me enjoy project management much more than LeanKit. It might sound silly that the UI makes so much of a difference to me, but …
Our company uses LeanKit, Pivotal Tracker, and Trello. It all depends on what team you're on. There's even a team that just does KanBan on a whiteboard. In the end, I would tank LeanKit above Pivotal Tracker, but below Trello. The differences are relatively subtle between …
Both VersionOne and Trello are good products. VersionOne is for the real hardcore Agile shops who want to track and report on everything related to the Agile process. Trello is a tool that works for Agile, but really is just a simple list making/tracking tool. Both tools serve …
I have used Trello, which is not as robust for tracking and customizing workflows as LeanKit is. It does not scale well to big teams. JIRA is the standard project management software but does not support Kanban well.
Nearly all the other tools I evaluated against are free, so that's one area where LeanKit is not as competitive. LeanKit does allow the experience to be much more customizable, though.
Being from QA I prefer Spiratest and QC for the fact my team can do all our work in one program and it is linked. But the tech department as a whole prefers Leankit as it is the tool of choice based on ease of use and overall performance.
While LeanKit was not designed for project and task management, we selected it because of its collaborative nature as a project and task management platform for our marketing team. It was also selected because our engineering and product management teams were using Leankit. We …
We’ve evaluated other integration tools—OpsHub, Jama Connect Interchange, and Symphony from agosense—and selected Planview TaskTop Hub because of its ease of use, scalability, and flexibility for managing and extending the integration concepts with new tools.
JIRA Align does not synch items outside of JIRA and Azure Dev Ops; TT Hub is specifically utilized to address connections to various other SDLC application.
AgilePlace is a great way for teams, or individuals, to bring visibility to the work in process and in their backlog. The color coding and icon use helps to quickly analyze the type of work or status of the work. The product team is doing a good job at listening to their user's feedback and implementing improvements. Where it falls short is when reporting needs to occur.
If used correctly in the hub/spoke model it can be very effective. If not implemented in this manner, it can lead to a lot of customizations to accommodate.
Okta Integration: We love using SSO for all our SaaS apps, and as new team members join, they can be automatically joined to the appropriate LeanKit boards.
Filtering and viewing: Can filter and refine by several fields as well as custom fields. Assigned Users, Tagged, Card Type, Date, etc
Their analytics and reporting can be helpful for PMs, especially if they have several teams they oversee.
LeanKit isn't the best designed Kanban system I've seen, but overall it's pretty usable. The boards I've used are pretty complex, so it can be difficult to find things. I found that searching and filtering for specific cards was somewhat of a challenge. Dragging a card from one lane to another is kind of a fun way to get things done though.
A great integration tool, which comes with a wide range of supported end tools. Planview TaskTop Hub works with an integration concept that maximizes the scalability and flexibility of integrations across more than just two tools. For example, from our experience, we started with the integration between Jama Connect and Jira. We were able to extend our integration concept to a new tool, Pro Cloud Server, by ourselves. The element was synced within 10 minutes.
We're hosting Planview TaskTop Hub by ourselves. The availability was good until now. A part of that, we have a strict plan for the quality control on any update of both Hub and End tools to avoid as much as possibily any disruptions.
Planview TaskTop Hub does generate traffic for some end tools. It is still in an acceptable range. For certain kind of retry to resolve issue in synchronizing relationships, an additional manual attention was required.
Every time I have reached out to the AgilePlace support team I have received a timely response in addition to professional & personal feedback. Their consultants are knowledgeable and the management team is happy to jump in and help when needed.
I was considering giving a rating between 9 and 10. Overall, the support has been very good so far. However, I have noticed that the members of the support team have varying levels of know-how about Planview TaskTop Hub. When a ticket about a complex technical issue reaches a member such as Christoph T., Sr. Customer Engineer, the analysis is done thoroughly, and a sustainable solution is provided. With other members of the support team, the experience might be different.
We had a very good collaboration with the enabling team from Tasktop in 2018. The enablement program was adequately structured, starting with building an integration concept based on use cases of the synchronized data. The training provided a good foundation for us to operate and maintain the tool. The tool administration and architecture were straightforward.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration. In the end, we picked Planview LeanKit because of several reasons: Aesthetics: The look was much more clean and professional. Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement. API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it. Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.