awork vs. Planview AgilePlace

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.

• 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

• 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

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

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.

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

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.