Kanban Tool vs. Planview AgilePlace

Kanban is well suited for a fast-paced working environment for larger teams who want continuous communication with users. Kanban is good for rapid development and daily meetings for updates and statuses. Kanban is less suited for smaller teams or groups who don't require collaboration and constant communication with involved users. Kanban is time-consuming and it takes additional effort outside of your regular work to maintain and manage the tool.

Incentivized

This tool enables the visual management needed in many offshore teams to easily and quickly see the pending work, work in progress and completed work.For teams that work with a waterfall methodology and do not have AGILE internalized, I believe there are other solutions from Planview or other providers.

• It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach).
• It provides a good collaborative space to have multiple folks commenting on multiple tasks.
• It does a good job of managing very basic visual elements of an agile development cycle.

Incentivized

• Ability to color code cards based on type, giving better visibility to the variety of tasks a team handles
• Ability to set deadline dates and have those dates easily visible
• Flexibility in design the kanban board. It is easy to add a lane or make a change on the fly. Work doesn't have to stop and a long process created to make simple layout changes.
• Movement of cards is easy as well as the ability to connect cards to show dependencies.

• Kanban does not show the task or story clearly. You have to open the project separately to view the details of the project.
• Kanban gives a higher level project management view but it lacks customization and personal settings features.
• I would like to see Kanban provide mobile access to their tool, data, and board. This would be very useful for all companies and provide an increase in efficiency and productivity.

Incentivized

• Planview LeanKit currently can't or should not be used as a central spot for data and collaboration. Particularly attachments are not well-handled.
• The portable side of Planview LeanKit is really lacking.
• We would appreciate some options to group or stack cards.

Incentivized

We are more likely than not to renew our use of Kanban. Even with its limits, it still is a good product that fulfills our needs.

Incentivized

Perfect tool to manage requirement backlog

Incentivized

Again, this is a strong tool for software teams using Agile that are distributed across multiple geographies. It can be good for co-located teams too, but there are better platforms on the market like JIRA that provide a more built-out story.

Incentivized

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

Very minimal outages

Incentivized

Never experienced major slowness

Incentivized

This is the best tool I had a chance to work with- since I started to use it I saved a lot of time and I made my work go smoothly.

It solves all our needs at this time.

Incentivized

Very easy.

Incentivized

We've only tried JIRA Agile and KanbanFlow before. Kanban Tool was the one that our team actually liked and enjoyed working with. Also - it's been much easier to get started with and to understand than some of the other two (JIRA in particular). Although JIRA has many more features that we would have possibly used, the user feedback on it was so poor we were afraid that the negativity would create time wasted and less "job satisfaction" amongst the team.

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 it really does. Trello is also sleeker than LeanKit, but I still prefer Asana because it has more customization options and a better interface. We are actually going to look into switching to ClickUp because we wanted something with a better UI. ClickUp seems to have a great UI with a lot of customization options.

Incentivized

Good use cases for small/large teams

Incentivized

• Better communication and organization of ongoing projects.
• We are a very small team, with many areas to work on. Having everything in one system gives us a lot of visibility.
• Greatly reduced costs from using other tools that were much more expensive.

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