Celoxis vs. Kanban Tool

Celoxis is a great option if you are looking for an affordable, easy to use, easy to integrate project manegement solution. It is very powerful for waterfall project management. I evaluated more than 15 platforms and could not find any with a close evaluation in terms of cost-benefit to Celoxis. Of course there are more powerfull tools, for 10 times the price. So far, for project management, there hasn't been a requirement I haven't been able to solve with some work. It really lacks features for Agile methodologies, even if it provides a Kanban view, so far it doesn't provide and additional agile artifacts. If an organization has already reached a very mature project management practice and needs to improve on program and portfolio management, Celoxis won't provide any useful feature. If the organization has the resources (skills and time mostly) to develop some workflows and customization, it might work but with a limit. Hopefully Celoxis addresses these features in the near future.

Incentivized

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

• Project planning
• Time log
• Efforts analysis vs plan

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

• Support is at times slow to respond.
• Not new user-friendly.
• Not able to pull in closer or zoom the interface.

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

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 used an evalaution matrix built with input of several stakeholders in the company. In the end the matrix included 100 features (non of them was price related). The matrix was heavily focused on waterfall project management, agile related features were only 5 out of 100 features. Features were labeled as mandatory, required or optional. Products which lacked a mandatory feature (like providing technical support) were disqualified. Then a price vs features evaluation was made and only the products with the best combination were seleced to continue: Celoxis, ITM Platform and Mission Control. A final technical evaluation was made comparing the full evaluation but also the evaluation of only the 40 required features. Overall, Celoxis was the better evaluated (76% vs 65% of the second place), for the 40 required features, Celoxis got 91% against 78% of number 2. In the end we chose Celoxis even when it had higher licensing cost.

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.

• Positive in most cases

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.