Planview AgilePlace vs. Zenhub

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.

Zenhub is incredible for the below areas: Burndown Charts, Release Reports, Velocity Tracking, Control Points Charts, Cumulative Flow Diagrams And if there is a bottleneck in your workflow, ZenHub identifies it. The most important aspect is serving as a collaboration tool for areas that are impeding implementation projects. For example when working with non-standard ERPs and having to document ERP integrations this tool is very helpful

Incentivized

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

Incentivized

• ZenHub continually adds to its reporting suite-- that truly allows you to track forward motion and see what issues may be the cause of any delays.
• Both our technical and non-technical staff can understand and use the functionality.
• We like the flexibility of being able to provide labels to our stories that can be customized to the way our company does things--- such as knowing if an epic is part of a module or a stream.
• We also like the flexibility of the number and labeling of the pipelines--- again, very adaptable to our organization.
• The filtering is very useful--- with and/or conditions, and allows people on different projects, doing different functions, an easy way to view what is important to them.

Incentivized

• The formatting of what they call "cards" could be better. They can be clunky if you have a lot of text in just one.
• Needs better support for media, attachments.
• Not the most pretty interface in my opinion, though it works.

Incentivized

• Sometimes, updates to a GitHub project can get lost if they're made through ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.
• It's great to be able to see your projects from within ZenHub, but sometimes you'll need to check in on the GitHub project itself, as well.
• I've run into some problems with updates getting lost on occasion. I think this happens when you do the update from within ZenHub instead of from GitHub itself. I also don't have quite as much control over my issues or milestones from within ZenHub.

Incentivized

we are happy with the tool and the service and continuos improvement of the tool so there is no need yet to change to another one.

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.

Incentivized

Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.

Incentivized

Not experienced any outage

Incentivized

Larger boards take longer to load

Incentivized

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.

Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.

Incentivized

Very easy.

Incentivized

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.

Incentivized

Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello we were doing everything twice, things got dropped, etc.

Incentivized

Good use cases for small/large teams

Incentivized

• Our team meetings are more direct and quick to get through thanks to the better visibility of the workload
• Easily being able to move cards between team lanes gives instant visibility to where the responsibility for the next step is needed.

• We are now able to determine output potential from our development resources based on points assignment.
• We were able to successfully implement an Agile methodology in our department.
• We have been able to better track tasks.
• We have used the releases feature to group our task to business release expections and easily filter.

Incentivized