Kanban Tool vs Replicon Polaris PSA

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.

It is perfect for inputing time sheets, time offs and expenses. It is hosted on the cloud, so accessible from anywhere, and even from mobile. It should nonetheless do just that, as it is not suited to track the work that you are doing or details about it. It is completely useless in that case.

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

• Many of our staff members work on multiple projects. Replicon PSM is ideal for managers to track all staff hours just by running a simple report.
• It's so easy use & maintain.
• Support team is really impressive, seem to know their product.
• Reporting is a breeze.

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

• Though the technical support staff are always very nice, sometimes they don't seem to understand exactly what the issue is based on our explanation. There have been several times when I've ended up solving the issue on my own without their assistance, despite numerous emails and phone calls. Could be a language barrier issue, perhaps they could receive more training in how companies are actually using the software on a daily basis.
• Employee time sheets have to be approved by project managers and supervisors prior to my final approval. However, when viewing the time sheets in list form, there is no way for me to tell whether a time sheet has been approved by everyone else. I have to manually open each one and hover over the approver link. It would be helpful if there was a column in the list showing which approvers still need to approve it.
• There have been a few times when time sheets were accidentally deleted by approvers. In order to retrieve them, we've had to contact Replicon support and have a backup instance of the information created. It would be great if perhaps there was some sort of archive or recently deleted section that could be accessed right away without having to go through Replicon support, a folder or something that would hold on to recently deleted files for a few days or a week just in case they needed to be retrieved.
• Some of our projects have more than one project manager. Replicon currently allows for co-managers to be assigned to a project, but this status does not seem to include that co-manager in the approval of time sheets and expenses. We have had to manually create an approval path to include that second manager. It would be nice if co-managers would automatically be included in those approval paths.

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.

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.

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.

We used to track time on JIRA on the tickets. This was good enough for time tracking, but didn't integrate efficiently with accounting software, so accountants had to replicate manually the data from JIRA to their software in order to bill clients. Using Replicon made things much easier for them.

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

• No negative; we just use it for timesheets.