Kanban Tool vs. Orangescrum

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 is a good thing for medium/large companies for inside the company and/or for interacting with remote employees/freelancers. As the program facilitates the interaction between employees and managers it speeds up the distribution of tasks and allows managers to identify possible problems on the fly. For indie developers - it's a little expensive.

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

• We tested the free version of the program. It improved communication within the team.
• Allowed to trace performance and time spent on tasks. Each team member was aware of the status of the tasks and could plan their work.
• Simplified interaction with managers, as it could present the results in the form of Gantt charts.

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

• The program interface is overloaded. Especially when there is little time for a detailed description of the tasks.
• I would like a faster way to publish the result at the completion of the task.
• Projects and tasks are two different workspaces/pages. Personally, it would be more convenient to combine these things.

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

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.

Trello was excellent, but we did not choose it because of the price and relatively positive feedback from employees using Orangescrum who wanted the easiest and fastest way to create reports so as not to be distracted from work (as a two-click report).

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.

• It accelerated the work of the team, but the mastering of the program interface was slow.
• The interface is not intuitive. It proved to be quite complicated.
• For managers, the program has facilitated reporting and streamlined team tracking.

Incentivized