Kanban Tool is a visual project management application based on Kanban that helps companies visualize workflow, track project progress, analyze and improve business processes. Some key features include: time tracking and time reports, real-time collaboration and Kaban analytics.
$6
per month per user
Pop
Score 9.7 out of 10
N/A
The makers of Screenhero now offer Pop, a remote collaboration platform with features like multiple mouse cursors, voice chat, and high definition screen resolution. Pop supports voice and video collaboration, screen sharing, multiplayer meetings, drawing and highlighting, and the ability to interact from a variety of devices (Mac, Windows, Linux, mobile devices, etc.).
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.
Copy/Paste works flawlessly from my computer to another screenhero users computer.
Screenhero works with screen-recording software, so not only can I pair-develop, I can take video of a pair development session.
I can't think of any reason why Screenhero wouldn't be suited for any situation. I would say that they need to bring back the option for a native app capability outside of the slack app like they did during the Slack merge transition.
EASY! A simply to use and understand UI cannot be understated. I needed no additional training and did not need to reference and support documentation to pick up and use Screenhero with my team. It's easy to add new folks to connect with, easy to call them, easy to end the call, and so forth. I would liken the UI to a more sleek Yahoo Instant Messenger (for those who remember that service!).
Painless. I rarely ever had connectivity issues or grainy audio/video quality. When I did occasionally encounter that (rough guess maybe 1 in 20), it usually cleared itself up after a few seconds. I think it's only ever "locked up" on me twice, meaning I had to disconnect and reconnect in order for the issue to be resolved. Overall, a painless experience.
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.
I'm not sure how to sign up right now. I guess until it's integrated into Slack as a full-blown feature it'll stay like that.
Most probably it'll be monetized as an extra feature.
This is true for most of the remote management solutions: security concerns. Slack had some break-ins in the past, giving remote control to your computer can be dangerous.
Another issue which is problematic for similar product too: watch out if there's an extra remote server is involved. Say you and your client you want to guide with Screenhero both log in to a remote server through RDP. Both the RDP and Screenhero capture hotkeys, and depenfing on if your other peer logs into screenhero on the server itself or his machine, things like copy-paste won't work because the RDP is interfering with the remote management software.
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.
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.
Screenhero being acquired by Slack was honestly the primary reason we selected it over TeamViewer. Our organization is heavily invested in Slack's enterprise solution, so choosing Screenhero was a pretty easy decision. On top of that, Screenhero delivers very well on its core competencies, so there doesn't seem to be a very good reason to not use it given its relationship with Slack.
