Gauss Box Projects vs. Kanban Tool

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

• 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

• 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

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

The integration with Teams is well suited. This works wonderful for my
company. Our team can easily prioritize tasks based on their importance.
It help our team identify and reduce inefficiencies in workflow. With
great visibility in data our team can make informed decisions. Ensuring
clear accountability and responsibility of team members

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.

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