Google Chat, formerly Hangouts Chat, is a collaboration tool competing with Slack, designed to make it easy for teams to be able to get their work done in one place. From direct messages to group conversations, Chat helps teams collaborate, and with dedicated, virtual rooms to house projects over time — plus threaded conversations — Chat helps users track progress and follow up tasks. Chat currently supports 28 languages and each room can support up to 8,000 members.
N/A
Kanban Tool
Score 9.2 out of 10
N/A
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.
Well suited for businesses of all sizes. HOWEVER, I would say keep the chat groups limited at the departmental level, ensure that your moderator or the individual responsible for the group keeps it on topic, and have your IT team monitor it from time to time. Google Chat gets used so much in our organization that we have rules and regs in our Employee Handbook regarding its proper use (and when used PROPERLY, it can be very effective).
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.
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.
The updates, support, general reviews on Google Chat are great everywhere. The development of the features is ongoing and this adds a great value to Google as a big company in the market. Other applications are limiting communication while Google Chat is allowing communication to grow. It is very easy to use it and teach others how to use Google Chat.
It's not perfect. There are occasional glitches, drop-outs, and it takes a bit to get everything loaded and working. But it is significantly better than Zoom or GoToMeeting when you're in instructional settings. I know my teacher friends here like it and the administrators and parents seem to be satisfied too.
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.
I have not needed to contact the support folks for Google Hangouts Chat, so I can't speak to this with any accuracy. The online instructions are fairly clearly written, so it is fairly intuitive to start with. I did not feel the need to use the support people anyway.
Prior to Google Hangouts, our company used Spark. Spark was not integrated into our email, therefore it couldn't be easily accessed in the same browser. With Spark we also couldn't search our emails for keywords in a conversation, searching had to be done manually. The one feature I enjoyed about Spark was a request to get a user's attention: If I had an urgent question and I wanted to ensure the recipient saw my message/question, I would request their attention and the message screen would pop up on their screen.
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.
