Kanban Tool vs. Project Insight

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

My rating would vary depending on the types of projects that need to be managed. Since I am in software, I don't think it was an excellent fit to manage software projects unless they are small projects with only a few tasks. On the other hand, if you are needing to manage a wide range of departments that are working on a single project with many moving pieces, then I would think that PI might be a better fit. Think of it as a jack of all trades, but master of none.

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

• History tracking for any changes made to data.
• Tracks all milestones and retains records for lifetime of account.
• Easy extracting for reporting purposes.

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

• Not a good fit for all types of projects
• Very Complex

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.

I found Project Insight somewhat opaque overall. I thought the training was sparse and answers to questions few and far in between. There was a lot of power there for the dedicated user/administrator. For me, who was a casual user and administrator, I found support lacking. I didn't administer Project Insight much, just some work on integrations with other tools.

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.

• When I got to the company where I used Project Insight, we had our own custom tool that fit the tasks that it was designed for but wouldn't grow with the company unless resources were put onto expanding capabilities. We needed something more.
• We replaced that tool with Redmine. It worked well and was easy to use, but it looked pretty dated when we got it, and since we didn't have many resources for managing, it looked dated after a few years without receiving upgrades. It was a decent tool for small teams that were focused on similar tasks. Redmine was much more straightforward than Project Insight and felt more reliable since we never had an issue with our internal servers. On the other hand, Redmine felt dated and didn't fit as many of the tasks that were needed. Redmine's price was right if you installed it locally and was probably still cheaper if you used their SAAS version.
• Jira, on the other hand, felt like an excellent tool for software teams. Jira had a great project and task management and felt right for a software team. Jira also had useful integrations, even with Project Insight. Jira seemed pretty unreliable, worse than Project Insight. Our team would have preferred Jira, but I think it didn't work for other teams.

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.

• Reduction in costs on materials (i.e. - paper documentation)
• Improved efficiency given that our field members need to report back on an hourly basis
• Web based platform allows anyone access to the same information

Incentivized