Kanban Tool vs. Taskworld

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 don't know anything about pricing, but if Taskworld were an inexpensive choice I would say it works fairly well for small to mid-sized companies with complex workflows. It's great for managing tasks that move through multiple-stage pipelines that aren't necessarily linear. However, depending on the price it's not worth the spend for all the technical difficulties it brought. Our company was relatively small (60 employees) and yet we constantly faced "server issues" and bugs and even software-wide crashes that seriously impacted our ability to do business. If you choose to go with Taskworld, be sure you have a solid disaster-management plan in place just in case, because chances are you'll experience bugs on a weekly basis

• 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

• Task Management - It's super easy to track progress on Taskworld. If your team keeps up with it, you'll never wonder where in the project someone is, because it's marked.
• Project checklists - Having these to organize out smaller portions of the tasks makes everything so much easier and helps keep track of progress.

Incentivized

• 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

• Taskworld crashed ALL THE TIME. It was so frustrating. You'd notice certain functions not working (like adding an additional location or reassigning a task) and then the whole thing would go down. We lost at least 3 individual business days due to Taskworld acting up.
• We often requested features and bug fixes that took forever to be resolved. Taskworld staff was responsive, but issues took too long to resolve. As a small example, the GIF functionality of chat and task communication was down for weeks with no explanation.
• Small glitches were frequent and obnoxious. We had to clear caches all the time in hopes that we'd be able to use Taskworld the way it was intended. There were many times employees didn't get notified of their "@ mentions" or weren't seeing notifications at all. It was a nightmare of death by a thousand cuts.

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.

I can't say too much about the support we've gotten from Taskworld, because we haven't needed it. There haven't been any issues we've to have to reach out about because it works too well. Given the quality of the application, I'm sure the quality of the support follows.

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.

We used Basecamp very briefly before switching over to Taskworld. Basecamp wasn't nearly as dynamic as Taskworld and served more as a static archive than an active workflow software.

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

• Efficient task assigning and management
• No stories left behind! It's too easy to track what's been worked on.

Incentivized