Kanban Tool vs. ZenTao

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

I am very glad about the working speed of this tool. The comfort and support it has provided us in project management are worth appreciating because Project management is a big deal and using ZenTao has made it easy and fun for us as we can as a team better collaborate. But some of its features need to be fixed.

• 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

• Story could be linked with product, sprint, test case, bug, which makes traceability so great.
• Test module, with test case, case library, test request, test report, very detailed.
• On-Premise available, the package is very small based on LAMPP
• SaaS version even cheaper without your own IT maintenance support.
• Price really affordable.
• API call is easy, so that we could do customizations.

• 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

• The function of ZenTao mobile version is a little weak.
• ZenTao users need to receive training before they start using the software, because for testers, the first use of the software may be a little complicated, and they cannot execute the same test case multiple times in the same test execution process.
• Although there are many reports built in. But if you want to get the data yourself，You have to know how to write SQL to customize your reports, which can a little bit challenging.

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

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

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.

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.

ZenTao defines bugs, tasks, and stories separately, not just an ISSUE. I can oversee the development from creating a Product Backlog to releasing the increment. I can also collect and record product feedback from the client and share with my team.

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

• We are delivering projects on time and can keep an eye on the progress of our projects.
• My team and I can better communicate on a project.
• As it is [in my experience], buggy it sometimes results in disturbing the whole working of our company.